#kubectl-logs

Can kubectl logs --previous reliably capture output from a CrashLoopBackOff container before rotation?

I am troubleshooting a Deployment whose Pods enter CrashLoopBackOff shortly after starting. I know the kubelet writes container stdout and stderr to files under /var/log/pods on the node, and that kubectl logs proxies those files through the API server, with --previous exposing the last terminated container instance. What I cannot pin down is the reliability

Community & Careers · Editorial question

kubeletcrashloopbackoffkubernetes