kubernetes storage_error ai_generated true

persistentvolumeclaim is in pending state: waiting for first consumer to be created before binding

ID: kubernetes/k8s-pvc-pending

Also available as: JSON · Markdown
85%Fix Rate
87%Confidence
60Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
8 active — — —

Root Cause

PVC stays Pending because of WaitForFirstConsumer binding mode, missing StorageClass, or insufficient storage capacity in the cluster.

generic

Workarounds

  1. 92% success For WaitForFirstConsumer, create a pod that uses the PVC — binding happens only when a pod is scheduled 
    Create a deployment or pod that references the PVC in its volumes section

    Sources: https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode

  2. 88% success Verify the StorageClass exists and is correctly configured: kubectl get storageclass 
    kubectl describe pvc <name> to check events and the requested StorageClass

    Sources: https://kubernetes.io/docs/concepts/storage/persistent-volumes/

Dead Ends

Common approaches that don't work:

  1. Repeatedly delete and recreate the PVC 80% fail

    If the StorageClass or provisioner is misconfigured, recreating won't help

  2. Switch StorageClass binding mode to Immediate 60% fail

    Breaks topology-aware scheduling — PV may be provisioned in wrong zone

Error Chain

Leads to:
Preceded by:
Frequently confused with: