Question

A developer creates a PersistentVolumeClaim requesting 10Gi with accessMode ReadWriteOnce. The cluster has three manually-created PersistentVolumes with no storageClassName set: PV-a (5Gi, ReadWriteOnce, Available), PV-b (20Gi, ReadWriteMany, Available), and PV-c (15Gi, ReadWriteOnce, Available). No StorageClass and no dynamic provisioner exist. Which PV will the PVC bind to?

Accepted Answer

PV-c, because it satisfies both the requested capacity and access mode

Answer

PV-a, because it is the smallest volume that most tightly matches the request

Answer

PV-b, because ReadWriteMany is a superset that also allows ReadWriteOnce access

Answer

The PVC stays Pending because no StorageClass is defined for dynamic provisioning