Persistent Volume Claims

A Persistent Volume (or PV) is simply a directory on a disk that is reachable from the containers inside a pod. Persistent Volume types are implemented as plugins in Kubernetes. This allows for both physical storage devices like NFS, NAS, and SSDs or cloud-based storage types like Amazon Elastic Block Store, Google Cloud Storage, or Azure disks access to a cluster via these plugin objects. PVs are either set up manually by an administrator or dynamically allocated using Storage Classes. It should be noted that PVs are independent of the individual Pods which utilizes them.

To get to this tab, go to the Storage > Persistent Volumes page. This view shows a significant amount of info about the PV.

The column data can be configured to show the following information.

• Name – The name of the volume

• Namespace – The namespace location of the PV

• Cluster – The cluster the PV is attached to

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

• Access Modes – This field indicates the CSI drivers specs

• Reclaim Policy – The reclaim policy can be either Delete or Retain. The default setting is Delete.

• Status – Defines whether the PV is bound or unbound

• Claim – This shows whether a PV is bound

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

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

• Created – When the PV was created

Examples

Below is an example of a YAML file for a PV.

PV YAML

apiVersion: v1
kind: PersistentVolume
metadata:
  name: foo-pv
spec:
  storageClassName: ""
  claimRef:
    name: foo-pvc
    namespace: foo
  ...