Question

Difficulty: EasyConfigure Azure Kubernetes Service (AKS)

An administrator plans to deploy a new Azure Kubernetes Service (AKS) cluster. The cluster pods must be assigned IP addresses directly from an existing Azure Virtual Network subnet to enable direct routing to other resources in the virtual network without performing Network Address Translation (NAT). Which network plugin should be selected during the AKS cluster configuration?

  1. Azure CNIAnswer
  2. B
    Kubenet
  3. C
    Azure Application Gateway Ingress Controller
  4. D
    Kubenet with Calico network policies

Answer

Azure CNI
The network plugin that meets this requirement is Azure CNI. When using Azure CNI, every pod receives a native IP address from the virtual network subnet. This allows pods to communicate directly with other resources in the virtual network, peered networks, or on-premises networks without using Network Address Translation (NAT).

Step-by-Step Solution

1
Analyze the requirements for pod IP allocation.
Pods must get IP addresses directly from the virtual network subnet and communicate without NAT.
This requirement determines the choice of AKS network plugin.
2
Compare the features of Kubenet and Azure CNI network plugins.
Azure CNI provides direct VNet IP allocation for pods, whereas Kubenet uses NAT and a separate logical IP space.
Matching the features to the requirement identifies the correct option.

Key Concept

Azure Kubernetes Service (AKS) network models (Azure CNI vs Kubenet)
Rate this question