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
Copy file name to clipboardexpand all lines: README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -1598,7 +1598,7 @@ In this section, we will explore value add features for administering & managing
1598
1598
$ kubectl get nodes
1599
1599
#
1600
1600
```
1601
-
[Auto-scaling](https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler) an AKS cluster is currently in public preview.
1601
+
The cluster can also be configured forautomatic scaling. You can read more about cluster **auto-scaling** featurein the [AKS documentation](https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler).
1602
1602
1603
1603
2. [Upgrade an AKS cluster](https://docs.microsoft.com/en-us/azure/aks/upgrade-cluster)
1604
1604
@@ -1612,9 +1612,9 @@ In this section, we will explore value add features for administering & managing
1612
1612
# List the available upgrade versions for the AKS cluster
1613
1613
$ az aks get-upgrades -g myResourceGroup -n akscluster -o table
1614
1614
#
1615
-
# Upgrade the AKS cluster to v1.15.7. Then confirm (y) the upgrade.
1615
+
# Upgrade the AKS cluster to v1.16.9. Then confirm (y) the upgrade.
1616
1616
# Be patient. The upgrade will run for a few minutes!
1617
-
$ az aks upgrade -g myResourceGroup -n akscluster --kubernetes-version 1.15.7
1617
+
$ az aks upgrade -g myResourceGroup -n akscluster --kubernetes-version 1.16.9
1618
1618
#
1619
1619
# Verify the nodes have been upgraded by checking the value under the 'KubernetesVersion' column
1620
1620
$ az aks show -g myResourceGroup -n akscluster -o table
@@ -1674,7 +1674,7 @@ In this section, we will explore a few advanced features provided by Kubernetes
1674
1674
# Verify only 1 in 4 API calls are being served by the Canary release
1675
1675
```
1676
1676
1677
-
Use **curl** and invoke the Claims API end-point in a loop. You will observe that version v1 of the Claims API will only be invoked once for every 3 invokations of version v2 of the API.
1677
+
Use **curl** and invoke the Claims API end-point in a loop. You will observe that version v2 of the Claims API will only be invoked once for every 3 invokations of version v1 of the API.
1678
1678
1679
1679
You can tweak the number of replicas in the v1 and v2 deployments to determine the ratio of each release which will receive live traffic.
0 commit comments