Library operators omit storageClassName on some PVCs and still receive dynamically provisioned volumes. What cluster setting explains that behavior?
Select an answer to reveal the explanation.
Short Explanation
Forget to pick a shelf label and the librarian still has a default shelf. Same idea: a StorageClass annotated as default quietly fills in when the PVC doesn’t name a class. That is convenience with a cost dial—know which class is default.
Full Explanation
Kubernetes can designate a default StorageClass (commonly via storageclass.kubernetes.io/is-default-class). PVCs that omit storageClassName use that default for dynamic provisioning. Omitting the field does not mean arbitrary static binding to any PV, API-server fake volumes, or an automatic emptyDir substitution.