Merge pull request #226433 from chasewilson/chase/region-update-cni-overlay

Updates Azure CNI Overlay Available Regions Update

Author: v-dirichards

articles/aks/azure-cni-overlay.md

@@ -7,7 +7,7 @@ ms.service: azure-kubernetes-service
 ms.subservice: aks-networking
 ms.topic: how-to
 ms.custom: references_regions
-ms.date: 02/03/2023
+ms.date: 02/06/2023
 ---
 
 # Configure Azure CNI Overlay networking in Azure Kubernetes Service (AKS)
@@ -17,12 +17,25 @@ The traditional [Azure Container Networking Interface (CNI)](./configure-azure-c
 With Azure CNI Overlay, the cluster nodes are deployed into an Azure Virtual Network (VNet) subnet, whereas pods are assigned IP addresses from a private CIDR logically different from the VNet hosting the nodes. Pod and node traffic within the cluster use an overlay network, and Network Address Translation (using the node's IP address) is used to reach resources outside the cluster. This solution saves a significant amount of VNet IP addresses and enables you to seamlessly scale your cluster to very large sizes. An added advantage is that the private CIDR can be reused in different AKS clusters, truly extending the IP space available for containerized applications in AKS.
 
 > [!NOTE]
-> Azure CNI Overlay is currently available only in the following regions:
-> - North Central US
-> - West Central US
-> - East US
-> - UK South
-> - Australia East
+> Azure CNI Overlay is currently **_unavailable_** in the following regions:
+> - East US 2
+> - Central US
+> - South Central US
+> - West US
+> - West US 2
+> - West US 3
+> - Southeast Asia
+> - Sweden Central
+> - France Central
+> - Norway East
+> - Switzerland North
+> - Qatar Central
+> - Jio India West
+> - Jio India Central
+> - UAE Central
+> - UAE North
+> - Brazil Southeast
+
 
 ## Overview of overlay networking
 
@@ -42,13 +55,13 @@ Ingress connectivity to the cluster can be achieved using an ingress controller
 
 Like Azure CNI Overlay, Kubenet assigns IP addresses to pods from an address space logically different from the VNet but has scaling and other limitations. The below table provides a detailed comparison between Kubenet and Azure CNI Overlay. If you do not want to assign VNet IP addresses to pods due to IP shortage, then Azure CNI Overlay is the recommended solution.
 
-| Area | Azure CNI Overlay | Kubenet |
-| -- | -- | -- |
-| Cluster scale | 1000 nodes and 250 pods/node | 400 nodes and 250 pods/node |
-| Network configuration | Simple - no additional configuration required for pod networking | Complex - requires route tables and UDRs on cluster subnet for pod networking |
-| Pod connectivity performance | Performance on par with VMs in a VNet | Additional hop adds minor latency |
-| Kubernetes Network Policies | Azure Network Policies, Calico | Calico |
-| OS platforms supported | Linux and Windows | Linux only |
+| Area                         | Azure CNI Overlay                                                | Kubenet                                                                       |
+|------------------------------|------------------------------------------------------------------|-------------------------------------------------------------------------------|
+| Cluster scale                | 1000 nodes and 250 pods/node                                     | 400 nodes and 250 pods/node                                                   |
+| Network configuration        | Simple - no additional configuration required for pod networking | Complex - requires route tables and UDRs on cluster subnet for pod networking |
+| Pod connectivity performance | Performance on par with VMs in a VNet                            | Additional hop adds minor latency                                             |
+| Kubernetes Network Policies  | Azure Network Policies, Calico                                   | Calico                                                                        |
+| OS platforms supported       | Linux and Windows                                                | Linux only                                                                    |
 
 ## IP address planning