Home > Storage > PowerMax and VMAX > Storage Admin > Persistent Storage for Containerized Applications on Kubernetes with PowerMax SAN Storage > Quota per Storage Class
One effortless way to manage and isolate storage consumption within the cluster is to create different storage pools in the array and map those pools to different Storage Classes.
Every Dell CSI has the option to select the pool to be associated with each different Storage Class.
cat <<EOF > storage-class-my-other-pool.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: powermax-my-other-pool
provisioner: csi-powermax
reclaimPolicy: Delete
parameters:
SRP: my-other-pool
SYMID: "000000000001"
EOF
kubectl create -f ./storage-class-my-other-pool.yaml
The CSI Driver for PowerMax by itself does not give visibility into subscription rates and utilization rates. Therefore, the PowerMax storage administrator must have proper monitoring in place for the storage pool. A good practice to track these metrics is to install CSM for Observability.
Note: The quota per StorageClass is used less often with the CSI Driver for PowerMax. It is a good practice to keep a single storage resource pool for the entire array.