Question

A developer submits a PersistentVolumeClaim that does not specify a storageClassName. The cluster has three StorageClasses defined, but the PVC remains Pending and no PersistentVolume is dynamically provisioned. You run 'kubectl get storageclass' and see that none of the classes shows '(default)' next to its name. What is the most likely cause and correct fix?

Accepted Answer

No StorageClass is marked as default; add the 'storageclass.kubernetes.io/is-default-class: "true"' annotation to the desired StorageClass so PVCs without a storageClassName use it.

Answer

The PVC requires an explicit accessModes field to trigger provisioning; add 'accessModes: [ReadWriteMany]' to the claim.

Answer

Dynamic provisioning only works when a matching PersistentVolume is manually pre-created; create a PV that matches the claim's size.

Answer

The provisioner field on the StorageClass must be set to 'kubernetes.io/no-provisioner'; update all three classes to enable dynamic provisioning.