Home > Storage > PowerFlex > White Papers > Container Storage Modules for Dell PowerFlex : Authorization Module > Over provisioning
A new SQL pod MSSQL04 with three volumes of sizes, 152Gi for data, 128Gi for temp, and 80Gi for logs is deployed so that the total storage capacity of all the PVCs deployed will be greater than the quota of 550Gi.
$ kubectl apply -f pv-mssql04.yaml -n tenant01
$ kubectl get pvc -n tenant01
NAME STATUS VOLUME CAPACITY AGE
data-logs01 Bound k8s-386bbdf308 08Gi 3d14h
data-logs02 Bound k8s-2cd0342937 16Gi 5m35s
data-logs03 Bound k8s-e8113153e8 56Gi 4m34s
data-logs04 2m34s
data-sql01 Bound k8s-5e2b6e83b1 16Gi 3d14h
data-sql02 Bound k8s-9fe7f9cd0d 32Gi 5m35s
data-sql03 Bound k8s-8b531a1c02 104Gi 4m34s
data-sql04 Bound k8s-8b531a1c02 152Gi 6s
data-temp01 Bound k8s-181a51820e 16Gi 3d14h
data-temp02 Bound k8s-4122efd023 32Gi 5m35s
data-temp03 Bound k8s-54cdd71c6d 104Gi 4m34s
data-temp04 2m34s
$ kubectl get pods -n tenant01
$ NAME READY STATUS RESTARTS AGE
mssql01-6479dbdd8d-csf8f 1/1 Running 0 3d14h
mssql02-74875bd5b8-6r4hp 1/1 Running 0 42m
mssql03-544468867b-vkv2v 1/1 Running 0 41m
mssql04-68789459cb-7888x 0/1 Pending 0 9s
In the above list of PVCs, only one PVC is created for the new pod. As the storage quota has been set to 550Gi, the PVCs are not created and are listed in an unbound state. The new pod will not be deployed since the total size of volumes required for deploying the pod exceeds the quota for the tenant.