Home > Storage > PowerMax and VMAX > Storage Admin > Persistent Storage for Containerized Applications on Kubernetes with PowerMax SAN Storage > Persistent Volumes
A PersistentVolume (PV) is a logical volume that is provisioned to containerized applications that require persistent storage. A PV usually corresponds to a single volume on the physical storage platform.
A PersistentVolume can be statically provisioned by the storage administrator or dynamically provisioned by the application owner with a PersistentVolumeClaim.
It is the role of the CSI Driver for PowerMax to create, format, and bind the volume to the Kubernetes worker node and attached container.
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
k8s-3401e3645a 8Gi RWO Delete Bound default/pgdata-pgset-2 powermax 36d
k8s-792f388c66 8Gi RWO Delete Bound test/pvol0 powermax 21d
k8s-792fe33166 16Gi RWO Delete Bound test/pvol1 powermax-xfs 21d
k8s-c71377055a 8Gi RWO Delete Bound default/pgdata-pgset-0 powermax 36d
k8s-c9c63c835a 8Gi RWO Delete Bound default/pgdata-pgset-1 powermax 36d
Note: As you can see, the PV name has a prefix (k8s in this example). It is a good practice to use a prefix to quickly identify and filter volumes attached to the Kubernetes cluster that provisions the volumes. Using a prefix makes the reconstruction easier if a disaster affects the Kubernetes cluster. Also, with version 2.5.0 and later, the volume identifier on the PowerMax system has the original namespace and PVC names in it.