Skip to content

Commit 7703243

Browse files
zioprotozioproto
authored
Update concepts-network.md
Fix links
1 parent afd539e commit 7703243

File tree

1 file changed

+9
-10
lines changed

1 file changed

+9
-10
lines changed

‎articles/aks/concepts-network.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -146,16 +146,15 @@ Both kubenet and Azure CNI provide network connectivity for your AKS clusters. H
146146

147147
The following behavior differences exist between kubenet and Azure CNI:
148148

149-
| Capability | Kubenet | Azure CNI | Azure CNI Overlay | Azure CNI Powered by Cilium |
150-
| -------------------------------------------------------------------------------------------- | --------------------------------- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
151-
| Deploy cluster in existing or new virtual network | Supported - UDRs manually applied | Supported | Supported | Supported |
152-
| Pod-pod connectivity | Supported | Supported | Supported | Supported |
153-
| Pod-VM connectivity; VM in the same virtual network | Works when initiated by pod | Works both ways | Works when initiated by pod | Works when initiated by pod |
154-
| Pod-VM connectivity; VM in peered virtual network | Works when initiated by pod | Works both ways | Works when initiated by pod | Works when initiated by pod |
155-
| On-premises access using VPN or Express Route | Works when initiated by pod | Works both ways | Works when initiated by pod | Works when initiated by pod |
156-
| Expose Kubernetes services using a load balancer service, App Gateway, or ingress controller | Supported | Supported | [You can't use Application Gateway as an Ingress Controller (AGIC) for an Overlay cluster.](https://learn.microsoft.com/en-us/azure/aks/azure-cni-overlay#limitations-with-azure-cni-overlay) | [Kubernetes services with internalTrafficPolicy=Local aren't supported](https://learn.microsoft.com/en-us/azure/aks/azure-cni-powered-by-cilium#limitations) |
157-
| Support for Windows node pools | Not Supported | Supported | [Preview](https://learn.microsoft.com/en-us/azure/aks/azure-cni-overlay#limitations-with-azure-cni-overlay) | [Available only for Linux and not for Windows.](https://learn.microsoft.com/en-us/azure/aks/azure-cni-powered-by-cilium#limitations) |
158-
149+
| Capability | Kubenet | Azure CNI | Azure CNI Overlay | Azure CNI Powered by Cilium |
150+
| -------------------------------------------------------------------------------------------- | --------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
151+
| Deploy cluster in existing or new virtual network | Supported - UDRs manually applied | Supported | Supported | Supported |
152+
| Pod-pod connectivity | Supported | Supported | Supported | Supported |
153+
| Pod-VM connectivity; VM in the same virtual network | Works when initiated by pod | Works both ways | Works when initiated by pod | Works when initiated by pod |
154+
| Pod-VM connectivity; VM in peered virtual network | Works when initiated by pod | Works both ways | Works when initiated by pod | Works when initiated by pod |
155+
| On-premises access using VPN or Express Route | Works when initiated by pod | Works both ways | Works when initiated by pod | Works when initiated by pod |
156+
| Expose Kubernetes services using a load balancer service, App Gateway, or ingress controller | Supported | Supported | [You can't use Application Gateway as an Ingress Controller (AGIC) for an Overlay cluster.](azure-cni-overlay#limitations-with-azure-cni-overlay) | [Kubernetes services with internalTrafficPolicy=Local aren't supported](azure-cni-powered-by-cilium#limitations) |
157+
| Support for Windows node pools | Not Supported | Supported | [Preview](azure-cni-overlay#limitations-with-azure-cni-overlay) | [Available only for Linux and not for Windows.](azure-cni-powered-by-cilium#limitations) |
159158

160159
Regarding DNS, with both kubenet and Azure CNI plugins DNS are offered by CoreDNS, a deployment running in AKS with its own autoscaler. For more information on CoreDNS on Kubernetes, see [Customizing DNS Service](https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/). CoreDNS by default is configured to forward unknown domains to the DNS functionality of the Azure Virtual Network where the AKS cluster is deployed. Hence, Azure DNS and Private Zones will work for pods running in AKS.
161160

0 commit comments

Comments
 (0)