Skip to content

Commit 8019770

Browse files
Update availability-zones.md
1 parent f17ffc2 commit 8019770

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/aks/availability-zones.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
9494

9595
Next, use the [kubectl describe][kubectl-describe] command to list the nodes in the cluster and filter on the `topology.kubernetes.io/zone` value. The following example is for a Bash shell.
9696

97-
```azurecli-interactive
97+
```bash
9898
kubectl describe nodes | grep -e "Name:" -e "topology.kubernetes.io/zone"
9999
```
100100

@@ -113,7 +113,7 @@ As you add more nodes to an agent pool, the Azure platform automatically distrib
113113

114114
With Kubernetes versions 1.17.0 and later, AKS uses the newer label `topology.kubernetes.io/zone` and the deprecated `failure-domain.beta.kubernetes.io/zone`. You can get the same result from running the `kubelet describe nodes` command in the previous step, by running the following script:
115115

116-
```azurecli-interactive
116+
```bash
117117
kubectl get nodes -o custom-columns=NAME:'{.metadata.name}',REGION:'{.metadata.labels.topology\.kubernetes\.io/region}',ZONE:'{metadata.labels.topology\.kubernetes\.io/zone}'
118118
```
119119

@@ -154,7 +154,7 @@ Name: aks-nodepool1-28993262-vmss000004
154154

155155
You now have two more nodes in zones 1 and 2. You can deploy an application consisting of three replicas. The following example uses NGINX:
156156

157-
```azurecli-interactive
157+
```bash
158158
kubectl create deployment nginx --image=mcr.microsoft.com/oss/nginx/nginx:1.15.5-alpine
159159
kubectl scale deployment nginx --replicas=3
160160
```

0 commit comments

Comments
 (0)