Question

Difficulty: MediumConfigure Azure Kubernetes Service (AKS)

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 /24/24 prefix, while a large number of pods must run on the cluster. Which AKS network configuration should you select to meet these requirements?

  1. Azure CNI with dynamic pod IP allocationAnswer
  2. B
    Kubenet networking with basic routing
  3. C
    Azure CNI with static IP allocation on a single subnet
  4. D
    Azure 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 /24/24 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

1
Analyze the networking requirements for the AKS cluster
The pods must have IP addresses that are directly routable in the virtual network, and the node subnet is limited to a /24/24 prefix.
Direct routability requires Azure CNI instead of Kubenet or Overlay models, but standard Azure CNI on a single /24/24 subnet will cause IP exhaustion.
2
Evaluate Azure CNI with dynamic pod IP allocation
This model separates node and pod subnets, allowing pod IPs to be dynamically allocated from a different, larger subnet.
By using a separate subnet for pods, the node subnet does not run out of IP addresses, and pods still receive directly routable IPs from the virtual network space.

Key Concept

Azure Kubernetes Service (AKS) network models and IP address planning
Rate this question