☁️ Free practice test question from: KCNA (KCNA)

Dynamic Provisioning: Kubernetes automatically creates a new PersistentVolume (PV) that exactly matches your PVC requirements using a storage class.

Static Provisioning: You're telling Kubernetes to use only pre-existing PVs that have already been created in the cluster.

When you set storageClassName: "" (empty string) in a PVC spec, you're instructing Kubernetes to only use already provisioned and available PVs rather than dynamically provisioning new ones.

This is in contrast to dynamic PV provisioning, where "the volume will always be of the exact size requested in the PVC spec."

When you use the empty string setting, here's what happens:

1. Kubernetes looks at all available PVs in the cluster (ones not already bound to other PVCs)

2. It filters these PVs based on matching criteria like access modes and labels

3. Among the matching PVs, it selects one that satisfies the resource requirements

4. Importantly, if there isn't an exact size match, Kubernetes will use a larger PV if available