Question

Difficulty: HardConfigure Azure Kubernetes Service (AKS)

An administrator is deploying a new Azure Kubernetes Service (AKS) cluster named `aks-prod` to host a microservices application. The corporate network security team requires that all pods must be able to communicate directly with on-premises databases over an existing ExpressRoute connection without using Network Address Translation (NAT). The virtual network `VNet1` has the address space 10.200.0.0/1610.200.0.0/16 and contains a subnet named `Subnet-AKS` (10.200.1.0/2410.200.1.0/24). The cluster is expected to scale up to 1515 nodes, and each node must support a maximum of 3030 pods. Which of the following configuration settings must be selected during the deployment of `aks-prod` to satisfy the requirements? (Select two.)

  1. Configure the cluster to use the Azure CNI network plugin.Answer
  2. B
    Configure the cluster to use the Kubenet network plugin.
  3. Deploy the cluster to a new subnet configured with an address prefix of 10.200.2.0/2310.200.2.0/23 or larger.Answer
  4. D
    Deploy the cluster to `Subnet-AKS` and set the maximum pods per node to 3030.
  5. E
    Deploy the cluster to `Subnet-AKS` and configure the pods to use the 10.244.0.0/1610.244.0.0/16 address space.

Answer

Configure the cluster to use the Azure CNI network plugin and deploy the cluster to a new subnet configured with an address prefix of 10.200.2.0/2310.200.2.0/23 or larger.
To satisfy the requirement of direct communication without NAT, the Azure CNI network plugin must be configured because it assigns IP addresses directly from the virtual network to the pods. To prevent IP exhaustion in the subnet, the cluster must be deployed to a subnet with an address prefix of 10.200.2.0/2310.200.2.0/23 or larger, which accommodates the 470470 IP addresses required (15 nodes+450 pods+5 reserved IPs15 \text{ nodes} + 450 \text{ pods} + 5 \text{ reserved IPs}).

Step-by-Step Solution

1
Determine the required network plugin model.
Azure CNI must be used.
The corporate policy requires direct, NAT-less communication from the pods to the on-premises database. Kubenet routes pod traffic outside the VNet using SNAT on the node's IP address. Azure CNI integrates pods directly into the virtual network, assigning them routable IPs.
2
Calculate the total number of IP addresses required for the cluster under Azure CNI.
At least 470470 IP addresses are required.
Using Azure CNI, the IP requirement formula is: Nodes + (Nodes * Max Pods per Node) + 55 Azure-reserved IPs. Calculating for 1515 nodes and 3030 pods per node: 15+(15×30)+5=15+450+5=47015 + (15 \times 30) + 5 = 15 + 450 + 5 = 470 IP addresses.
3
Select the correct subnet sizing to accommodate the IP addresses.
A new subnet of size /23/23 or larger is required.
The existing `Subnet-AKS` is a /24/24 subnet, which yields 232245=2512^{32-24} - 5 = 251 usable IP addresses, leading to IP exhaustion. A /23/23 subnet provides 232235=5072^{32-23} - 5 = 507 usable IP addresses, which satisfies the 470470 IP address requirement.

Key Concept

Azure Kubernetes Service (AKS) network plugin selection and IP address planning.
Estimated Time:2m 0s
Rate this question