Skip to content

Commit 7e64c88

Browse files
committed
Update for sovereign cloud limitation
1 parent d9656a8 commit 7e64c88

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/aks/azure-cni-overlay.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Like Azure CNI Overlay, Kubenet assigns IP addresses to pods from an address spa
3939
| Network configuration | Simple - no additional configuration required for pod networking | Complex - requires route tables and UDRs on cluster subnet for pod networking |
4040
| Pod connectivity performance | Performance on par with VMs in a VNet | Additional hop adds minor latency |
4141
| Kubernetes Network Policies | Azure Network Policies, Calico, Cilium | Calico |
42-
| OS platforms supported | Linux and Windows Server 2022(Preview) | Linux only |
42+
| OS platforms supported | Linux and Windows Server 2022(Preview) | Linux only |
4343

4444
## IP address planning
4545

@@ -98,6 +98,7 @@ Azure CNI Overlay has the following limitations:
9898
- Windows support is still in Preview
9999
- Windows Server 2019 node pools are **not** supported for Overlay
100100
- Traffic from host network pods is not able to reach Windows Overlay pods.
101+
- Sovereign Clouds are not supported
101102
- Virtual Machine Scale Sets (VMAS) are not supported for Overlay
102103
- Dualstack networking is not supported in Overlay
103104
- You can't use [DCsv2-series](/azure/virtual-machines/dcv2-series) virtual machines in node pools. To meet Confidential Computing requirements, consider using [DCasv5 or DCadsv5-series confidential VMs](/azure/virtual-machines/dcasv5-dcadsv5-series) instead.

0 commit comments

Comments
 (0)