Your company plans to deploy an Azure Kubernetes Service (AKS) cluster in an existing virtual network. The virtual network has a limited subnet address space, and you must conserve IP addresses. The design must ensure that pods do not receive IP addresses directly from the virtual network subnet, and instead use network address translation (NAT) to communicate with other resources. Which two configuration settings should you select when deploying the AKS cluster to meet these requirements?
- Set the network plugin to Kubenet.Cevap
- Specify a separate, non-overlapping Pod CIDR address range.Cevap
- CSet the network plugin to Azure Container Networking Interface (CNI).
- DEnable Azure CNI with dynamic IP allocation.
- EConfigure Azure Route Server integration for pod routing.
Cevap
To configure the AKS cluster to conserve IP addresses using NAT, you must set the network plugin to Kubenet and specify a separate, non-overlapping Pod CIDR address range.
The correct configuration settings are to set the network plugin to Kubenet and specify a separate, non-overlapping Pod CIDR address range. Kubenet is a basic routing model where pods do not receive IP addresses from the virtual network subnet, which conserves subnet IP addresses. Instead, pods receive IPs from a specified Pod CIDR range, and their traffic is routed through the nodes using NAT.
Adım Adım Çözüm
Anahtar Kavram
Azure Kubernetes Service (AKS) networking models, specifically the differences between Kubenet (NAT-based) and Azure CNI (VNet-integrated) plugins.