CrashLoopBackOff

A container status meaning the container keeps exiting after it starts, so the kubelet is waiting longer and longer before restarting it.

In more detail

It tells you the process started and then stopped; it does not say why. Read the exit code and the logs of the previous run with kubectl logs --previous, and check probes and resource limits. A healthy GitOps sync or rollout can still produce pods in this state.

Example

kubectl logs web --previous

Related terms

Related guides

Taught in

References

Certification courses