Kubernetes New Added 9 September 2026

Kubernetes: pod has unbound immediate PersistentVolumeClaims

The scheduler will not place the pod because its claim has no volume yet. With WaitForFirstConsumer binding a moment of this is normal, so it only matters when it persists: then the storage class is missing, the provisioner is unhealthy, or the claim asks for an access mode the driver does not support.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

# Start at the claim and its events, not at the pod
kubectl describe pvc data-web-0
kubectl get storageclass

# A claim with no class needs a default to exist
kubectl get sc -o jsonpath='{range .items[*]}{.metadata.name}{" "}{.metadata.annotations}{"\n"}{end}'

# Is the provisioner running, and what is it saying?
kubectl -n kube-system logs -l app=ebs-csi-controller --tail=50

# ReadWriteMany never binds on a block driver: use a file based class
kubectl get pvc data-web-0 -o jsonpath='{.spec.accessModes}{"\n"}'

# A StatefulSet claim keeps the old class: recreating the pod will not fix it

How to diagnose Kubernetes errors

Kubernetes errors are best read as a state machine that got stuck. Pending means the scheduler could not place the pod (resources, taints, or an unbound volume). ImagePullBackOff means kubelet could not fetch the image (name, credentials, or registry). CrashLoopBackOff means the container starts and exits, so the answer is in the container's own logs. OOMKilled means the kernel killed it for exceeding its memory limit. Each state points at a different subsystem, and kubectl describe almost always contains the exact reason in its events.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Start with kubectl describe pod <name> and read the Events section at the bottom. It names the precise failure, including registry errors and scheduling constraints.
For CrashLoopBackOff, read the previous container's logs: kubectl logs <pod> --previous. The current container may not have produced output yet.
Check resource pressure with kubectl top pod and kubectl top node, and compare against the pod's requests and limits.
Test RBAC directly: kubectl auth can-i <verb> <resource> --as=system:serviceaccount:<ns>:<sa>. This answers permission questions definitively.
For networking, confirm the Service has endpoints (kubectl get endpoints) before suspecting DNS, Ingress or the CNI.

Tools worth reaching for

kubectl describe
kubectl logs --previous
kubectl auth can-i
kubectl top
kubectl events --sort-by=.lastTimestamp
k9s

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

kubernetes.io

Related Kubernetes errors

See all 34 Kubernetes errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.