A county PVC sets storageClassName: fast and stays unbound until a matching volume appears. What normally causes the PersistentVolume to be created automatically?
Select an answer to reveal the explanation.
Short Explanation
Filing a PVC that names StorageClass fast is like submitting a work order to the “fast” shop—the provisioner on that class builds the disk and the PV shows up bound to your claim. The scheduler, DNS, and kube-proxy are not the disk factory.
Full Explanation
Dynamic provisioning is initiated when a PersistentVolumeClaim references a StorageClass (or the default class). The associated provisioner creates a PersistentVolume that satisfies the claim and binds it. Schedulers place Pods, CoreDNS resolves names, and kube-proxy implements Service networking—none of those components provision PVs from a StorageClass.