Question

You statically provision a PersistentVolume named data-pv with a capacity of 50Gi, accessModes of ReadWriteOnce, and no storageClassName set. A developer then creates a PersistentVolumeClaim requesting 20Gi of storage with ReadWriteOnce and no storageClassName. The PVC binds successfully to data-pv. When the developer runs 'df -h' inside the pod that mounts this PVC, what usable capacity will the mounted volume report for a typical backing filesystem?

Accepted Answer

Approximately 50Gi, because the PVC binds to the entire PV and there is no per-claim capacity enforcement on a statically provisioned volume

Answer

Exactly 20Gi, because Kubernetes enforces the requested capacity as a hard quota on the mounted filesystem

Answer

0Gi, because the capacity mismatch prevents the volume from being usable despite the binding

Answer

35Gi, the average of the PV capacity and the PVC request