Persistent Volume Claims in Kubernetes

Persistent Volumes and Persistent Volume Claims are two separate objects in Kubernetes: an administrator creates a set of Persistent Volumes and a user creates Persistent Volume Claims to use the storage.
Once the PVC are created, Kubernetes binds the Volumes to Claims based on the request and properties set on the Volume:

• Sufficient Capacity
• Access Modes
• Volume Modes
• Storage Class

Every PVC is bound to a single PV. Hovewer, if there are multiple possible matches for a single Claim and you would like specifically use the particular Volume you could still use Labels and Selectors to bind to the right Volumes.
If there are no Volumes available the PVC will remain in the Pending state until newer Volumes made available.

Example of PVC:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: myclaim
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 500Mi

To view PVC use:

kubectl get pvc

To delete PVC run:

kubectl delete pvc myclaim