Skip to content

Commit d6e505b

Browse files
Merge pull request #256476 from wedaly/aks-networking-concepts-revision
Revise AKS network concepts sections on Azure CNI Overlay and Cilium
2 parents c716c5f + 996df47 commit d6e505b

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

articles/aks/concepts-network.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -116,13 +116,17 @@ Nodes use the [Azure CNI][cni-networking] Kubernetes plugin.
116116

117117
For more information, see [Configure Azure CNI for an AKS cluster][aks-configure-advanced-networking].
118118

119-
### Azure CNI overlay networking
119+
### Azure CNI Overlay networking
120120

121-
[Azure CNI Overlay][azure-cni-overlay] represents an evolution of Azure CNI, addressing scalability and planning challenges arising from the assignment of VNet IPs to pods. It achieves this by assigning private CIDR IPs to pods, which are separate from the VNet and can be reused across multiple clusters. Unlike Kubenet, where the traffic dataplane is handled by the Linux kernel networking stack of the Kubernetes nodes, Azure CNI Overlay delegates this responsibility to Azure networking.
121+
[Azure CNI Overlay][azure-cni-overlay] represents an evolution of Azure CNI, addressing scalability and planning challenges arising from the assignment of VNet IPs to pods. It achieves this by assigning private CIDR IPs to pods, which are separate from the VNet and can be reused across multiple clusters. Additionally, Azure CNI Overlay can scale beyond the 400 node limit enforced in Kubenet clusters. Azure CNI Overlay is the recommended option for most clusters.
122122

123123
### Azure CNI Powered by Cilium
124124

125-
In [Azure CNI Powered by Cilium][azure-cni-powered-by-cilium], the data plane for Pods is managed by the Linux kernel of the Kubernetes nodes. Unlike Kubenet, which faces scalability and performance issues with the Linux kernel networking stack, [Cilium][https://cilium.io/] bypasses the Linux kernel networking stack and instead leverages eBPF programs in the Linux Kernel to accelerate packet processing for faster performance.
125+
[Azure CNI Powered by Cilium][azure-cni-powered-by-cilium] uses [Cilium](https://cilium.io) to provide high-performance networking, observability, and network policy enforcement. It integrates natively with [Azure CNI Overlay][azure-cni-overlay] for scalable IP address management (IPAM)
126+
127+
Additionally, Cilium enforces network policies by default, without requiring a separate network policy engine. Using eBPF programs and a more efficient API object structure, Azure CNI Powered by Cilium can scale beyond [Azure Network Policy Manager's limits of 250 nodes / 20K pod][use-network-policies].
128+
129+
Azure CNI Powered by Cilium is the recommended option for clusters that require network policy enforcement.
126130

127131
### Bring your own CNI
128132

0 commit comments

Comments
 (0)