A city platform team wants SSD-backed volumes for municipal databases created automatically via CSI. What must their StorageClass define to enable that dynamic path?
Select an answer to reveal the explanation.
Short Explanation
A StorageClass is like a catalog card that says which workshop builds your disks. The provisioner name is the workshop—your CSI driver—and parameters are the build options (SSD, IOPS, and so on). Without that provisioner pointer, Kubernetes has no factory to call when a PVC shows up.
Full Explanation
A StorageClass selects the volume plugin or CSI driver responsible for dynamic provisioning through its provisioner field and optional parameters. When a PVC references that class, the provisioner creates a matching PersistentVolume. Retain-only static workflows, hostPath templates, and Ingress classes do not define CSI dynamic provisioning.