How do I debug Kubernetes CrashLoopBackOff?

Short answer: Start with pod events and the previous container logs. CrashLoopBackOff is usually caused by process exit, failed probes, missing config, image issues, or startup dependency failures.

Steps

1. Paste kubectl get pods, describe pod, events, and previous container logs.
2. Check restart count, exit code, last state, image pull status, and probe failures.
3. Verify ConfigMaps, Secrets, service accounts, resource limits, and startup dependencies.
4. Run the smallest kubectl command that confirms the suspected failure mode.

Related tools