Persistent Volume Claims

A PersistentVolumeClaim (or PVC) is a user requested storage option, similar to a Pod. Pods however access PVs through Persistent Volume Claims. Since Pods consume node resources, and PVCs consume the resources allocated to the PV, Pods can request a specific level of resources (CPU and Memory) from the node for these resources.

These volume claims can also request different access modes and sizes to accommodate users unique needs. Because users require other configurations, different options are available using the StorageClass resource.

The columns are available to be modified by clicking on the gear icon, which can show more info. The available columns are as follows.

• Name – The name of the volume

• Namespace – The namespace location of the PV

• Cluster – The cluster the PV is attached to

• Status – Defines whether the PV is bound or unbound

• Label – This is the field that the user defines for the PVC

• Volume – The name of the PV the PVC is attached to

• Capacity – The amount of storage capacity provided for in the PV

• Access Modes – This field indicates the CSI drivers specs

• Storage Class – The name of the CSI driver used in the storage class

• Created – When the PV was created

Below, is an example of a PVC YAML file.

YAML

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: foo-pvc
  namespace: foo
spec:
  storageClassName: "" # Empty string must be explicitly set otherwise default StorageClass will be set
  volumeName: foo-pv
  ...