☸️ Kubernetes errors

Pod states and cluster errors: CrashLoopBackOff, ImagePullBackOff, OOMKilled.

CodeErrorWhat it means
kubectl connection refused kubectl: The connection to the server localhost:8080 was refused — did you specify the right host or port? kubectl has no usable kubeconfig, so it falls back to localhost:8080 — or the cluster API server is unreachab…
CrashLoopBackOff Kubernetes: CrashLoopBackOff The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
CreateContainerConfigError Kubernetes: CreateContainerConfigError — secret / configmap not found Kubernetes can’t build the container’s configuration — usually a referenced Secret, ConfigMap or key doesn’t…
ImagePullBackOff Kubernetes: ImagePullBackOff / ErrImagePull The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachab…
OOMKilled Kubernetes: OOMKilled (exit code 137) The container used more memory than its limit, and the kernel killed it.
Evicted Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage The kubelet removed the pod because its node ran short of memory or disk.
FailedScheduling Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available The scheduler can’t find a node that satisfies the pod’s resource requests, selectors, taints or volume const…