Storage Classes and Dynamic Provisioning

Every PersistentVolume you created in the previous article required an admin to carve out storage manually, write a PV manifest, and apply it before any Pod could use it. That works when you have five volumes. It stops working at fifty, and it completely falls apart when developers spin up PVCs across dozens of namespaces without filing a ticket first.

StorageClasses solve this by defining what kind of storage you offer and letting Kubernetes provision the actual volumes on demand. The PVC says "I need 10Gi of fast SSD storage," the StorageClass tells the provisioner how to create it, and the PV appears automatically. No admin intervention, no YAML by hand.