Question

Difficulty: MediumConfigure Azure Kubernetes Service (AKS)

An administrator is deploying a new Azure Kubernetes Service (AKS) cluster named aks-corp to run internal workloads. The cluster nodes will be deployed into an existing virtual network subnet with the IP address range 172.16.0.0/20172.16.0.0/20. The virtual network is peered with an on-premises network that uses the range 192.168.1.0/24192.168.1.0/24. You decide to use the Kubenet network plugin. Which combination of Pod CIDR and Service CIDR is valid for this deployment?

  1. Pod CIDR: 10.244.0.0/1610.244.0.0/16; Service CIDR: 10.0.0.0/1610.0.0.0/16Answer
  2. B
    Pod CIDR: 172.16.16.0/20172.16.16.0/20; Service CIDR: 172.16.0.0/20172.16.0.0/20
  3. C
    Pod CIDR: 192.168.1.0/24192.168.1.0/24; Service CIDR: 10.0.0.0/1610.0.0.0/16
  4. D
    Pod CIDR: 10.244.0.0/1610.244.0.0/16; Service CIDR: 10.244.0.0/1610.244.0.0/16

Answer

Pod CIDR: 10.244.0.0/1610.244.0.0/16; Service CIDR: 10.0.0.0/1610.0.0.0/16
The correct configuration uses Pod CIDR 10.244.0.0/1610.244.0.0/16 and Service CIDR 10.0.0.0/1610.0.0.0/16. These ranges do not overlap with the node subnet range of 172.16.0.0/20172.16.0.0/20, the peered network range of 192.168.1.0/24192.168.1.0/24, or each other, which satisfies the AKS networking prerequisites.

Step-by-Step Solution

1
Identify the existing and peered network ranges that must be avoided to prevent IP address overlaps.
The node subnet range is 172.16.0.0/20172.16.0.0/20 and the peered on-premises network range is 192.168.1.0/24192.168.1.0/24.
AKS requires that neither the Pod CIDR nor the Service CIDR overlap with these existing network spaces.
2
Ensure that the proposed Pod CIDR and Service CIDR do not overlap with each other.
The Pod CIDR and Service CIDR must be distinct, non-overlapping IP address spaces.
Internal cluster routing will fail if pods and services share the same subnet ranges.
3
Evaluate the options against these criteria.
Only the configuration with Pod CIDR 10.244.0.0/1610.244.0.0/16 and Service CIDR 10.0.0.0/1610.0.0.0/16 satisfies all isolation requirements.
This configuration avoids all overlaps with the node subnet, the peered network, and each other.

Key Concept

AKS Kubenet IP Addressing and Overlap Rules
Rate this question