Skip to content

Commit 431c447

Browse files
authored
Merge pull request #17898 from MicrosoftDocs/VanMSFT-patch-1
fixing codeblocks for kubectl
2 parents bede065 + 24f3c1b commit 431c447

1 file changed

Lines changed: 11 additions & 11 deletions

File tree

docs/linux/tutorial-sql-server-containers-kubernetes.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Create an SA password in the Kubernetes cluster. Kubernetes can manage sensitive
6060

6161
The following command creates a password for the SA account:
6262

63-
```azurecli
63+
```console
6464
kubectl create secret generic mssql --from-literal=SA_PASSWORD="MyC0m9l&xP@ssw0rd"
6565
```
6666

@@ -105,7 +105,7 @@ Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/pers
105105
106106
1. Create the persistent volume claim in Kubernetes.
107107
108-
```azurecli
108+
```console
109109
kubectl apply -f <Path to pvc.yaml file>
110110
```
111111

@@ -117,15 +117,15 @@ Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/pers
117117

118118
1. Verify the persistent volume claim.
119119

120-
```azurecli
120+
```console
121121
kubectl describe pvc <PersistentVolumeClaim>
122122
```
123123

124124
`<PersistentVolumeClaim>` is the name of the persistent volume claim.
125125

126126
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:
127127

128-
```azurecli
128+
```console
129129
kubectl describe pvc mssql-data
130130
```
131131

@@ -139,7 +139,7 @@ Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/pers
139139

140140
1. Verify the persistent volume.
141141

142-
```azurecli
142+
```console
143143
kubectl describe pv
144144
```
145145

@@ -238,7 +238,7 @@ In this step, create a manifest to describe the container based on the SQL Serve
238238

239239
1. Create the deployment.
240240

241-
```azurecli
241+
```console
242242
kubectl apply -f <Path to sqldeployment.yaml file>
243243
```
244244

@@ -259,7 +259,7 @@ In this step, create a manifest to describe the container based on the SQL Serve
259259

260260
1. Verify the services are running. Run the following command:
261261

262-
```azurecli
262+
```console
263263
kubectl get services
264264
```
265265

@@ -275,13 +275,13 @@ In this step, create a manifest to describe the container based on the SQL Serve
275275

276276
1. You can also verify the container is running as non-root by running the following command:
277277

278-
```azurecli
278+
```console
279279
kubectl.exe exec <name of SQL POD> -it -- /bin/bash
280280
```
281281

282282
and then run 'whoami' you should see the username as mssql. Which is a non-root user.
283283

284-
```azurecli
284+
```console
285285
whoami
286286
```
287287

@@ -314,15 +314,15 @@ To verify failure and recovery, you can delete the pod. Do the following steps:
314314

315315
1. List the pod running SQL Server.
316316

317-
```azurecli
317+
```console
318318
kubectl get pods
319319
```
320320

321321
Note the name of the pod running SQL Server.
322322

323323
1. Delete the pod.
324324

325-
```azurecli
325+
```console
326326
kubectl delete pod mssql-deployment-0
327327
```
328328

0 commit comments

Comments
 (0)