An administrator is configuring a new Azure Kubernetes Service (AKS) cluster in an existing virtual network. The corporate network security team requires that all pods receive IP addresses that are directly routable within the virtual network. However, to conserve IP address space, the subnet allocated for the AKS cluster nodes is limited to a prefix, while a large number of pods must run on the cluster. Which AKS network configuration should you select to meet these requirements?
- Azure CNI with dynamic pod IP allocationAnswer
- BKubenet networking with basic routing
- CAzure CNI with static IP allocation on a single subnet
- DAzure CNI Overlay networking
Answer
Azure CNI with dynamic pod IP allocation
Azure CNI with dynamic pod IP allocation solves the IP exhaustion issue by deploying nodes and pods in separate subnets. The nodes subnet can be small (such as a subnet), while the pods are allocated IPs from a larger, separate subnet. Because both subnets are part of the virtual network, the pod IP addresses remain directly routable within the virtual network.
Step-by-Step Solution
Key Concept
Azure Kubernetes Service (AKS) network models and IP address planning