PVC stuck in Pending
A Pending PVC hasn’t been bound to a PersistentVolume yet. Sometimes that’s expected, and the events tell you which case you’re in.
Diagnose in order
Section titled “Diagnose in order”kubectl describe pvc <name>and read the events.- Check the StorageClass it asks for exists:
kubectl get storageclass, and look for(default)if the claim doesn’t name one. - Check the CSI driver’s controller pods are running (usually in
kube-systemor the driver’s own namespace).
What the events mean
Section titled “What the events mean”| Event message | Meaning |
|---|---|
waiting for first consumer to be created before binding |
Normal with WaitForFirstConsumer. Binding happens when a pod using it is scheduled. |
no persistent volumes available for this claim and no storage class is set |
No default StorageClass, and none named in the claim |
storageclass.storage.k8s.io "fast" not found |
Typo in storageClassName, or the class doesn’t exist in this cluster |
ProvisioningFailed with a backend error |
The storage system refused: quota, size limits, unsupported access mode, permissions of the driver’s credentials |
waiting for a volume to be created, either by external provisioner ... or manually with no progress |
The CSI provisioner isn’t running or isn’t watching this class |
Name a StorageClass that exists, mark one as default, fix the CSI driver, or fix the backend error. If a pod is waiting for a WaitForFirstConsumer claim and also Pending, look at the pod’s FailedScheduling event instead: the claim is waiting on the pod, not the other way round.
Read next: Storage and CSI.