Kubernetes errors
Exact Kubernetes error codes and states, explained from the emitting component outward. Start with evidence; follow the deeper links only when the first checks support them.
Open the Kubernetes technology indexKubernetes CrashLoopBackOff
A container repeatedly starts and exits, so the kubelet applies an increasing delay before trying again.
Kubernetes ImagePullBackOff
The node cannot retrieve a container image and is delaying subsequent pull attempts.
Kubernetes OOMKilled
The container exceeded available memory at its cgroup or node boundary and was killed.
Kubernetes FailedScheduling: insufficient resources
The scheduler cannot find a node that satisfies the Pod's resource requests and placement constraints.
Kubernetes FailedMount
Kubernetes could not attach, prepare or mount one or more volumes required by the Pod.
Kubernetes RBAC forbidden
The request was authenticated, but the active authoriser did not permit the requested verb, resource and scope.
Kubernetes context deadline exceeded
A Kubernetes operation did not complete before its caller's deadline expired, indicating latency or unavailability somewhere in the request path.
Kubernetes readiness probe connection refused
The kubelet reached the Pod network but no process accepted the readiness probe connection at the configured address and port.
Kubernetes Pod evicted by node pressure
The kubelet terminated a Pod to reclaim a constrained node resource such as memory, filesystem space or inodes.
Kubernetes Node NotReady
The control plane no longer considers a node healthy enough to host normal workload traffic.
Kubernetes Service has no endpoints
A Kubernetes Service currently has no ready backend addresses to receive traffic, even though its virtual IP and DNS name may still exist.
Follow Kubernetes failures and fixes
One useful weekly email with new error references, tools, integration notes and production lessons. No daily noise.