CrashLoopBackOff
The container starts, exits and is restarted with a growing delay. Find the reason in the previous attempt's logs and its exit code.
Guides
Kubernetes troubleshooting guides.
What the error means, how to find its cause with kubectl, and how to fix it — for the problems that fill a cluster's event log. Every guide works without PodSteer; each ends with what PodSteer does about the same problem.
OOMKilled
The container used more memory than its limit and the kernel killed it. Confirm it, measure the real peak, then size the limit or fix the leak.
ImagePullBackOff
The node cannot fetch the container image. The event message says whether the image is missing, the registry refused, or it could not be reached.
Pod stuck in Pending
No node can take the pod. The scheduler's FailedScheduling event names every constraint that ruled a node out.
CreateContainerConfigError
The kubelet cannot build the container's configuration: a ConfigMap, Secret or key it names is missing, or a security setting cannot be met.
Pod stuck in Terminating
The pod was deleted but has not gone. A finalizer, a process ignoring SIGTERM, or a node nobody can reach is holding it.
Evicted pods
A node ran short of memory, disk or process IDs and the kubelet reclaimed it by evicting pods — first those using more than they requested.
Node NotReady
The kubelet stopped reporting, or reported it cannot run pods. Its pods keep showing Running until they are evicted.
Running but not ready
The containers run, but readiness fails, so no Service sends the pod traffic. Check the probe, then the Service's endpoints.