infrastructure

Kubernetes Errors

Kubernetes pod statuses: ImagePullBackOff, CrashLoopBackOff, ErrImagePull, OOMKilled, CreateContainerConfigError, RunContainerError. Most issues trace to image pull, resource limits, or config maps/secrets.

K8s pod failures cluster around image (ImagePullBackOff, ErrImagePull), runtime (CrashLoopBackOff, RunContainerError), resources (OOMKilled, Evicted), and config (CreateContainerConfigError, InvalidImageName). `kubectl describe pod` and `kubectl logs --previous` are your first two commands. ImagePullBackOff = registry auth, missing tag, or typo.

Runtime (1)

CrashLoopBackOff

Pod Restart Loop

Your container starts, exits with a non-zero code (or is OOMKilled), the kubelet restarts it, it exits again — repeat. After several quick failures the kubelet enters CrashLoopBackOff, an exponential delay between restart attempts so you don't melt the node.

Configuration (1)

ImagePullBackOff

Cannot Pull Image

The kubelet failed to pull the container image and is now backing off retry attempts. Underlying error is one of ErrImagePull, ImagePullBackOff is the recovery loop. Causes are almost always image name/tag wrong, registry auth missing, registry rate-limit, or the image genuinely doesn't exist for the node's architecture.

Official docs

https://kubernetes.io/docs/tasks/debug/debug-application/

Support

https://kubernetes.io/community/

Runtime (1)

Configuration (1)

Related services