You are deploying a new Azure Kubernetes Service (AKS) cluster named `aks-finance` into an existing Azure virtual network. The deployment must meet the following requirements:
* The Kubernetes pods must receive IP addresses directly from a dedicated subnet in the virtual network, distinct from the subnet used by the cluster nodes.
* User application workloads must not run on the same virtual machines as the cluster's system pods.
Which two actions should you perform? (Select two.)
- Configure the cluster to use Azure CNI with dynamic pod IP allocation.Answer
- Apply the CriticalAddonsOnly=true:NoSchedule taint to the system node pool.Answer
- CConfigure the cluster to use Azure CNI Overlay networking.
- DConfigure the cluster to use Kubenet networking.
- ESet the mode of the application node pool to System.
Answer
Configure the cluster to use Azure CNI with dynamic pod IP allocation, and apply the CriticalAddonsOnly=true:NoSchedule taint to the system node pool.
Configuring Azure CNI with dynamic pod IP allocation allows pods to be assigned IP addresses from a dedicated subnet that is separate from the node subnet. Applying the CriticalAddonsOnly=true:NoSchedule taint to the system node pool ensures that only system pods, which have the appropriate tolerations, can be scheduled on the system nodes, thereby isolating user workloads.
Step-by-Step Solution
Key Concept
Azure Kubernetes Service (AKS) networking options (Azure CNI with dynamic IP allocation) and workload isolation using taints.