An administrator is configuring a new Azure Kubernetes Service (AKS) cluster named aks-retail. The cluster will be deployed in an existing virtual network (VNet) named VNet1. VNet1 has a single subnet named Subnet1 with the address prefix . Due to enterprise IP addressing constraints, no additional subnets can be created in VNet1, and VNet1 cannot be expanded. The cluster must support up to nodes and pods. The pods must be able to communicate with each other, and you must use Azure Network Policies to secure pod-to-pod traffic.
Which two network configuration options should you select to meet these requirements? (Select two.)
- Configure the network plugin to use Azure CNI with Overlay.Cevap
- BConfigure the network plugin to use Kubenet.
- Define a Pod CIDR block that does not overlap with the virtual network or peered networks.Cevap
- DConfigure the network plugin to use Azure CNI with dynamic pod IP allocation.
- EEnable Azure Network Policies on the Kubenet network plugin.
Cevap
Configure the network plugin to use Azure CNI with Overlay and define a Pod CIDR block that does not overlap with the virtual network or peered networks.
To support Azure Network Policies while preventing VNet IP address exhaustion and meeting the constraint of not adding new subnets, Azure CNI Overlay is the correct network model. Under Azure CNI Overlay, nodes receive IP addresses from the existing subnet, but pods receive IP addresses from a separate, non-overlapping Pod CIDR block that is defined outside the virtual network.
Adım Adım Çözüm
Anahtar Kavram
Azure CNI Overlay is designed to resolve VNet IP exhaustion by using a separate overlay address space for pods while supporting standard Azure Network Policies.