You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -105,7 +105,7 @@ Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/pers
105
105
106
106
1. Create the persistent volume claim in Kubernetes.
107
107
108
-
```azurecli
108
+
```console
109
109
kubectl apply -f <Path to pvc.yaml file>
110
110
```
111
111
@@ -117,15 +117,15 @@ Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/pers
117
117
118
118
1. Verify the persistent volume claim.
119
119
120
-
```azurecli
120
+
```console
121
121
kubectl describe pvc <PersistentVolumeClaim>
122
122
```
123
123
124
124
`<PersistentVolumeClaim>` is the name of the persistent volume claim.
125
125
126
126
In the preceding step, the persistent volume claim is named `mssql-data`. To see the metadata about the persistent volume claim, run the following command:
127
127
128
-
```azurecli
128
+
```console
129
129
kubectl describe pvc mssql-data
130
130
```
131
131
@@ -139,7 +139,7 @@ Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/pers
139
139
140
140
1. Verify the persistent volume.
141
141
142
-
```azurecli
142
+
```console
143
143
kubectl describe pv
144
144
```
145
145
@@ -238,7 +238,7 @@ In this step, create a manifest to describe the container based on the SQL Serve
238
238
239
239
1. Create the deployment.
240
240
241
-
```azurecli
241
+
```console
242
242
kubectl apply -f <Path to sqldeployment.yaml file>
243
243
```
244
244
@@ -259,7 +259,7 @@ In this step, create a manifest to describe the container based on the SQL Serve
259
259
260
260
1. Verify the services are running. Run the following command:
261
261
262
-
```azurecli
262
+
```console
263
263
kubectl get services
264
264
```
265
265
@@ -275,13 +275,13 @@ In this step, create a manifest to describe the container based on the SQL Serve
275
275
276
276
1. You can also verify the container is running as non-root by running the following command:
277
277
278
-
```azurecli
278
+
```console
279
279
kubectl.exe exec <name of SQL POD> -it -- /bin/bash
280
280
```
281
281
282
282
and then run 'whoami' you should see the username as mssql. Which is a non-root user.
283
283
284
-
```azurecli
284
+
```console
285
285
whoami
286
286
```
287
287
@@ -314,15 +314,15 @@ To verify failure and recovery, you can delete the pod. Do the following steps:
0 commit comments