Konubinix' opinionated web of thoughts

Persistent Volume Claim

fleeting

persistent volume claim

From https://kubernetes.io/docs/concepts/storage/persistent-volumes/

A PersistentVolumeClaim (PVC) is a request for storage by a user. It is similar to a Pod. Pods consume node resources and PVCs consume PV resources.

A PersistentVolumeClaim (PVC) is a request for storage by a user. It is similar to a Pod. pods consume node resources and PVCs consume PV resources. Pods can request specific levels of resources (CPU and Memory). Claims can request specific size and access modes

A control loop in the master watches for new PVCs, finds a matching PV (if possible), and binds them together.

PersistentVolumeClaim binds are exclusive, regardless of how they were bound. A PVC to PV binding is a one-to-one mapping

Claims will be bound as matching volumes become available

By specifying a PersistentVolume in a PersistentVolumeClaim, you declare a binding between that specific PV and PVC. If the PersistentVolume exists and has not reserved PersistentVolumeClaims through its claimRef field, then the PersistentVolume and PersistentVolumeClaim will be bound.

Pods access storage by using the claim as a volume. […] The cluster […] uses it to get the PersistentVolume backing the claim. The volume is then mounted to the host and into the Pod.

Notes linking here