Home > Storage > PowerFlex > White Papers > Container Storage Modules for Dell PowerFlex : Authorization Module > Deploying SQL pods
A new namespace is created in the Kubernetes cluster where the Authorization module and CSI Driver are installed. For demonstration purposes, a SQL Server pod is deployed, and multiple volumes of various sizes are attached to it. The deployment steps are as follows:
$ kubectl create namespace tenant01
$ kubectl apply -f pv-mssql01.yaml -n tenant01
$ kubectl get pv
NAME CAPACITY ACCESS MODES STORAGECLASS AGE
k8s-386bbdf308 8Gi RWO vxflexos 3d13h
k8s-181a51820e 16Gi RWO vxflexos 3d13h
k8s-5e2b6e83b1 16Gi RWO vxflexos 3d13h
$ kubectl get pvc -n tenant01
NAME STATUS VOLUME CAPACITY AGE
data-logs01 Bound k8s-386bbdf308 8Gi 3d13h
data-sql01 Bound k8s-5e2b6e83b1 16Gi 3d13h data-temp01 Bound k8s-181a51820e 16Gi 3d13h
$ kubectl apply -f mssql01.yaml -n tenant01
$ kubectl get pods -n tenant01
NAME READY STATUS RESTARTS AGE
mssql01-6479dbdd8d-csf8f 1/1 Running 0 3d13h
$ kubectl get pods -n tenant01
NAME READY STATUS RESTARTS AGE
mssql01-6479dbdd8d-csf8f 1/1 Running 0 3d13h
mssql02-74875bd5b8-6r4hp 1/1 Running 0 3d12h
mssql03-544468867b-vkv2v 1/1 Running 0 3d12h
$ 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-sql01 Bound k8s-5e2b6e83b1 16Gi 3d14h
data-sql02 Bound k8s-9fe7f9cd0d 32Gi 5m35s
data-sql03 Bound k8s-8b531a1c02 104Gi 4m34s
data-temp01 Bound k8s-181a51820e 16Gi 3d14h
data-temp02 Bound k8s-4122efd023 32Gi 5m35s
data-temp03 Bound k8s-54cdd71c6d 104Gi 4m34s
In the above section we deployed three pods, each having different volume sizes. These pods were deployed successfully because the specified quota for Tenant01 in the role Role_Tenant01 did not exceed 550Gi, as specified in the Role section.