PersistentVolumeClaims
A PVC stays in Pending. The cluster has a default StorageClass with volumeBindingMode: WaitForFirstConsumer. What is the most likely explanation?
volumeBindingMode: WaitForFirstConsumer
Choose one answer
The StorageClass is broken and must be deleted.
No Pod that uses the PVC has been scheduled yet, so provisioning is intentionally delayed.
PVCs always stay Pending until an admin approves them.
The PVC requested ReadWriteOnce, which is not supported.