☸

Kubernetes Pod States & Errors

k8s 1.3273 codes

Pod states, exit codes, probe failures, RBAC, storage and network errors

Showing 73 of 73 errors

Code	Message	Severity	Tier
CrashLoopBackOff	Container keeps crashing and restarting	ERROR	Common	→
ImagePullBackOff	Failed to pull container image with backoff	ERROR	Common	→
ErrImagePull	Failed to pull container image	ERROR	Common	→
OOMKilled	Container ran out of memory	ERROR	Notable	→
Evicted	Pod was evicted from the node	WARNING	Critical	→
InvalidImageName	Container image name is not valid	ERROR	Common	→
ContainerCreating	Pod is stuck in the ContainerCreating state	WARNING	Notable	→
CreateContainerConfigError	Error creating container configuration	ERROR	Common	→
RunContainerError	Error running the container	ERROR	Common	→
Pending (Insufficient cpu)	Pod cannot be scheduled due to insufficient CPU	WARNING	Notable	→
Pending (Insufficient memory)	Pod cannot be scheduled due to insufficient memory	WARNING	Notable	→
Pending (Taint Toleration)	Pod cannot be scheduled due to taints	WARNING	Critical	→
Forbidden (RBAC)	Action is forbidden by RBAC policy	ERROR	Notable	→
NotFound (resource)	The requested resource was not found	ERROR	Critical	→
Conflict (409)	Conflict updating a resource	WARNING	Critical	→
UnprocessableEntity (422)	The request is invalid	ERROR	Notable	→
PVCNotBound	PersistentVolumeClaim is not bound	WARNING	Notable	→
ConfigMapNotFound	A referenced ConfigMap was not found	ERROR	Common	→
SecretNotFound	A referenced Secret was not found	ERROR	Common	→
ConnectionRefused (API server down)	Cannot connect to the Kubernetes API server	CRITICAL	Common	→
ResourceQuotaExceeded	Resource creation forbidden by a ResourceQuota	WARNING	Critical	→
NodeNotReady	Node is not ready to accept pods	CRITICAL	Common	→
ExitCode 0	Container exited successfully	INFO		→
ExitCode 1	Application exited with a general error	ERROR	Notable	→
ExitCode 2	Misuse of shell builtins or incorrect usage	ERROR	Notable	→
ExitCode 125	Container failed to run — Docker/runtime error	ERROR	Notable	→
ExitCode 126	Command found but not executable	ERROR	Notable	→
ExitCode 127	Command not found in container	ERROR	Notable	→
ExitCode 128	Invalid exit argument passed to exit()	ERROR	Critical	→
ExitCode 137	Container killed by SIGKILL (OOM or manual kill)	CRITICAL	Common	→
Completed	Pod has finished successfully	INFO		→
Terminating	Pod is being deleted and awaiting graceful shutdown	WARNING	Notable	→
Error	Container exited with a non-zero exit code	ERROR	Notable	→
Init:CrashLoopBackOff	Init container is crashing repeatedly	ERROR	Common	→
Init:Error	Init container exited with an error	ERROR	Notable	→
Init:OOMKilled	Init container was killed due to out-of-memory	CRITICAL	Common	→
Init:ImagePullBackOff	Init container image cannot be pulled	ERROR	Notable	→
PodInitializing	Init containers are still running	INFO		→
RunningButNotReady	Pod is running but readiness probe is failing	WARNING	Notable	→
Unschedulable	Pod cannot be placed on any node	WARNING	Notable	→
CreateContainerError	Kubelet could not create the container	ERROR	Notable	→
PostStartHookError	postStart lifecycle hook failed	ERROR	Notable	→
PreStopHookError	preStop hook failed during pod termination	WARNING	Critical	→
DeadlineExceeded	Pod exceeded its activeDeadlineSeconds limit	ERROR	Notable	→
Liveness probe failed	Container killed by failing liveness probe	ERROR	Notable	→
Readiness probe failed	Pod removed from service endpoints due to failing readiness probe	WARNING	Notable	→
Startup probe failed	Container killed before startup probe passed	ERROR	Notable	→
Liveness probe timeout	Liveness probe did not respond within timeoutSeconds	WARNING	Notable	→
Pending (no nodes available)	No nodes exist in the cluster to schedule the pod	CRITICAL	Common	→
Pending (node selector mismatch)	nodeSelector or nodeAffinity does not match any node	WARNING	Notable	→
Pending (PodAffinityError)	Pod affinity or anti-affinity rules cannot be satisfied	WARNING	Notable	→
NodeMemoryPressure	Node is under memory pressure — pods may be evicted	WARNING	Notable	→
NodeDiskPressure	Node disk is full or nearly full	WARNING	Notable	→
Unauthorized (401)	Authentication failed — missing or invalid token	ERROR	Notable	→
ServiceAccountNotFound	Pod references a service account that does not exist	ERROR	Notable	→
TooManyRequests (429)	API server rate limit exceeded	WARNING	Notable	→
ServerTimeout (504)	API server request timed out	ERROR	Notable	→
BadRequest (400)	Malformed API request body rejected by the server	ERROR	Critical	→
FailedMount	Volume mount failed — pod cannot start	ERROR	Notable	→
VolumeMountError	Kubelet cannot mount the volume onto the node	ERROR	Notable	→
PVCPending	PVC waiting for storage class to provision a volume	WARNING	Notable	→
StorageClassNotFound	StorageClass referenced in PVC does not exist	ERROR	Notable	→
NetworkNotReady	CNI plugin not ready — pods cannot get network interfaces	ERROR	Common	→
EgressDenied	NetworkPolicy is blocking outbound traffic from the pod	WARNING	Notable	→
ServiceEndpointNotFound	No healthy pods are registered behind the service	WARNING	Notable	→
SchedulingGated	Pod is blocked from scheduling by a scheduling gate	WARNING	Notable	→
DisruptionTarget	Pod is being evicted by a disruption controller	WARNING	Notable	→
PodFailurePolicyMatch	Job pod failure matched a pod failure policy rule	WARNING	Notable	→
WaitingForPodScheduled	Init/sidecar container waiting for the pod to be scheduled	INFO	Critical	→
SidecarContainerStarting	Sidecar container is starting before main containers	INFO	Critical	→
ExitCode143	Container received SIGTERM but did not exit within grace period	WARNING	Notable	→
NodePIDPressure	Node is under PID pressure — too many processes running	ERROR	Common	→
ResourceQuotaExceededNamespace	Namespace resource quota exceeded for a specific resource type	ERROR	Common	→