Question

A developer creates a PersistentVolumeClaim requesting 5Gi with accessMode ReadWriteOnce, but the PVC remains stuck in 'Pending' status. The cluster has no manually created PersistentVolumes. You inspect the PVC and notice it does not specify a storageClassName field, and no default StorageClass is configured in the cluster. What is the most likely reason the PVC is not being bound?

Accepted Answer

Without a default StorageClass or an explicit storageClassName, dynamic provisioning cannot occur and no matching pre-provisioned PV exists to bind.

Answer

The requested size of 5Gi exceeds the maximum allowed for ReadWriteOnce volumes, which is capped at 1Gi.

Answer

ReadWriteOnce access mode requires at least two worker nodes to be available before a PVC can bind.

Answer

The PVC must include a reclaimPolicy of Retain in its spec before the scheduler will bind it to any volume.