Soru

Zorluk: OrtaConfigure Azure Kubernetes Service (AKS)

An organization is deploying a new Azure Kubernetes Service (AKS) cluster to host a critical application. The corporate security policy requires that all pods receive IP addresses directly from the virtual network (`VNet1`) to facilitate direct firewall auditing of pod traffic to on-premises databases. However, the primary subnet designated for the cluster nodes, `10.200.1.0/2410.200.1.0/24`, has a limited number of available IP addresses. To prevent IP address exhaustion on the node subnet while satisfying the security policy, which two configurations should the administrator implement? (Select two.)

  1. Configure the cluster to use the Azure CNI network plugin.Cevap
  2. Specify a separate subnet in the virtual network for dynamic pod IP allocation.Cevap
  3. C
    Configure the cluster to use the Kubenet network plugin and set the pod CIDR to match the node subnet.
  4. D
    Configure the cluster to use the Azure CNI Overlay network plugin.

Cevap

Configure the cluster to use the Azure CNI network plugin and specify a separate subnet in the virtual network for dynamic pod IP allocation.
To allow firewalls to audit individual pod traffic directly, pods must have IP addresses from the Azure Virtual Network, which requires the Azure CNI plugin. To avoid IP exhaustion on the node subnet, the administrator can configure dynamic pod IP allocation. This feature allows nodes to be deployed in one subnet while pods are allocated IPs from a completely separate subnet, saving IP space on the node subnet.

Adım Adım Çözüm

1
Analyze the networking requirements to determine the correct network plugin.
Since the security policy requires pods to have direct, auditable virtual network IP addresses, Azure CNI must be selected. Kubenet and Azure CNI Overlay are ruled out because they use internal or private CIDR spaces that NAT or encapsulate pod traffic.
Azure CNI is required to assign pods IP addresses directly from the Azure Virtual Network.
2
Address the node subnet IP address limitation.
Standard Azure CNI assigns IPs from the same subnet as the nodes, leading to rapid IP exhaustion. To prevent this, dynamic pod IP allocation must be configured.
Dynamic pod IP allocation allows the deployment of nodes in one subnet and the allocation of pod IPs from a separate subnet.
3
Configure the dedicated pod subnet during deployment.
By specifying a separate subnet for pod allocation, nodes only consume IPs for the host VMs, preserving the node subnet's IP addresses.
Assigning a separate subnet for pod allocation optimizes IP address usage and satisfies the security policy.

Anahtar Kavram

Azure Kubernetes Service (AKS) network models and dynamic pod IP allocation configuration.
Tahmini Süre:2m 0s
Bu soruyu puanla