You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/azure-cni-overlay.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,6 +63,18 @@ The following are additional factors to consider when planning pods IP address s
63
63
64
64
***Kubernetes DNS service IP address**: This is an IP address within the Kubernetes service address range that's used by cluster service discovery. Don't use the first IP address in your address range, as this address is used for the `kubernetes.default.svc.cluster.local` address.
65
65
66
+
## Network security groups
67
+
68
+
Pod to pod traffic with Azure CNI Overlay is not encapsulated and subnet [network security group][nsgs] rules are applied. If the subnet NSG contains deny rules that would impact the pod CIDR traffic, make sure the following rules are in place to ensure proper cluster functionality (in addition to all [AKS egress requirements][aks-egress]):
69
+
70
+
* Traffic from the node CIDR to the node CIDR on all ports and protocols
71
+
* Traffic from the node CIDR to the pod CIDR on all ports and protocols (required for service traffic routing)
72
+
* Traffic from the pod CIDR to the pod CIDR on all ports and protocols (required for pod to pod and pod to service traffic, including DNS)
73
+
74
+
Traffic from a pod to any destination outside of the pod CIDR block will utilize SNAT to set the source IP to the IP of the node where the pod is running.
75
+
76
+
If you wish to restrict traffic between workloads in the cluster, [network policies][aks-network-policies] are the recommended solution.
77
+
66
78
## Maximum pods per node
67
79
68
80
You can configure the maximum number of pods per node at the time of cluster creation or when you add a new node pool. The default for Azure CNI Overlay is 30. The maximum value that you can specify in Azure CNI Overlay is 250, and the minimum value is 10. The maximum pods per node value configured during creation of a node pool applies to the nodes in that node pool only.
@@ -148,3 +160,6 @@ To learn how to utilize AKS with your own Container Network Interface (CNI) plug
0 commit comments