Skip to content

Commit 82727a5

Browse files
committed
acrolinx
1 parent ca51f51 commit 82727a5

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/aks/istio-deploy-addon.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ export LOCATION=<location>
3030
The add-on requires Azure CLI version 2.57.0 or later installed. You can run `az --version` to verify version. To install or upgrade, see [Install Azure CLI][azure-cli-install].
3131

3232
## Query available Istio add-on revisions
33-
You can use the command below to find information about which Istio add-on revisions are available in a region and their compatibility with AKS cluster versions:
33+
To find information about which Istio add-on revisions are available in a region and their compatibility with AKS cluster versions, use:
3434

3535
```azurecli-interactive
3636
az aks mesh get-revisions --location <location> -o table
@@ -39,11 +39,11 @@ az aks mesh get-revisions --location <location> -o table
3939

4040
## Install Istio add-on
4141
### Revision selection
42-
If you enable the add-on without specifiying a revision, a default supported revision will be installed for you
42+
If you enable the add-on without specifying a revision, a default supported revision is installed for you.
4343

4444
If you wish to select a revision instead:
45-
1. Use the `get-revisions` command in the [previous step](#query-available-istio-add-on-revisions) to check which revisions are available for different AKS cluster versions in a region.
46-
1. Based on the available revisions, you can include a `--revision asm-X-Y` flag in in the enable command you use for mesh installation
45+
1. Use the `get-revisions` command in the [previous step](#query-available-istio-add-on-revisions) to check which revisions are available for different AKS cluster versions in a region
46+
1. Based on the available revisions, you can include a `--revision asm-X-Y` flag in the enable command you use for mesh installation.
4747

4848
### Install mesh during cluster creation
4949

@@ -102,7 +102,7 @@ istiod-asm-1-18-74f7f7c46c-xfdtl 1/1 Running 0 2m
102102

103103
## Enable sidecar injection
104104

105-
To automatically install sidecar to any new pods, annotate your namespaces with the revision label corresponding to the control plane revision currently installed. If you are unsure which revision is installed, use:
105+
To automatically install sidecar to any new pods, annotate your namespaces with the revision label corresponding to the control plane revision currently installed. If you're unsure which revision is installed, use:
106106
```bash
107107
az aks show --resource-group ${RESOURCE_GROUP} --name ${CLUSTER} --query 'serviceMeshProfile.istio.revisions'
108108
```
@@ -125,12 +125,12 @@ kubectl apply -f <(istioctl kube-inject -f sample.yaml -i aks-istio-system -r as
125125
You can either deploy the sample application provided for testing, or trigger sidecar injection for existing workloads.
126126

127127
### Existing applications
128-
If you have existing applications to be added to the mesh, ensure their namespaces are labelled as in the previous step, and then restart their deployments to trigger sidecar injection:
128+
If you have existing applications to be added to the mesh, ensure their namespaces are labeled as in the previous step, and then restart their deployments to trigger sidecar injection:
129129
```bash
130130
kubectl rollout restart -n <namespace> <deployment name>
131131
```
132132

133-
Verify that sidecar injection succeeded by looking for the `istio-proxy` container in the describe output, ex:
133+
Verify that sidecar injection succeeded by ensuring all containers are ready and looking for the `istio-proxy` container in the `kubectl describe` output, for example:
134134
```bash
135135
kubectl describe pod -n namespace <pod name>
136136
```

0 commit comments

Comments
 (0)