Skip to content

Commit 9657fb2

Browse files
Merge pull request #228805 from chasewilson/chase/cniExistingUpgrade
Adds 'Upgrade existing clusters' to CNI Overlay doc
2 parents 830545c + 54a9fd7 commit 9657fb2

File tree

1 file changed

+18
-2
lines changed

1 file changed

+18
-2
lines changed

articles/aks/azure-cni-overlay.md

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: allensu
66
ms.subservice: aks-networking
77
ms.topic: how-to
88
ms.custom: references_regions
9-
ms.date: 02/24/2023
9+
ms.date: 02/27/2023
1010
---
1111

1212
# Configure Azure CNI Overlay networking in Azure Kubernetes Service (AKS)
@@ -45,7 +45,7 @@ Like Azure CNI Overlay, Kubenet assigns IP addresses to pods from an address spa
4545
| Network configuration | Simple - no additional configuration required for pod networking | Complex - requires route tables and UDRs on cluster subnet for pod networking |
4646
| Pod connectivity performance | Performance on par with VMs in a VNet | Additional hop adds minor latency |
4747
| Kubernetes Network Policies | Azure Network Policies, Calico, Cilium | Calico |
48-
| OS platforms supported | Linux and Windows Server 2022 | Linux only |
48+
| OS platforms supported | Linux and Windows Server 2022 | Linux only |
4949

5050
## IP address planning
5151

@@ -152,6 +152,22 @@ location="westcentralus"
152152
az aks create -n $clusterName -g $resourceGroup --location $location --network-plugin azure --network-plugin-mode overlay --pod-cidr 192.168.0.0/16
153153
```
154154

155+
## Upgrade existing clusters
156+
157+
To update an existing cluster to use Azure CNI overlay, there are a couple prerequisites:
158+
159+
1. The cluster must use Azure CNI without the pod subnet feature.
160+
1. The cluster is _not_ using network policies.
161+
1. The Overlay Pod CIDR needs to be an address range that _does not_ overlap with the existing cluster's VNet.
162+
163+
To update a cluster, run the following Azure CLI command.
164+
165+
```azurecli
166+
az aks update --name $clusterName --resource-group $resourceGroup --network-plugin azure --network-plugin-mode overlay --pod-cidr $overlayPodCidr
167+
```
168+
169+
This will perform a rolling upgrade of nodes in **all** nodepools simultaneously to Azure CNI overlay and should be treated like a node image upgrade. During the upgrade, traffic from an Overlay pod to a CNI v1 pod will be SNATed(Source Network Address Translation)
170+
155171
## Next steps
156172

157173
To learn how to utilize AKS with your own Container Network Interface (CNI) plugin, see [Bring your own Container Network Interface (CNI) plugin](use-byo-cni.md).

0 commit comments

Comments
 (0)