QuestionQ238

Network Design

A company is developing an internet-facing application hosted on an Amazon Elastic Kubernetes Service (Amazon EKS) cluster. The company uses the Amazon VPC Container Network Interface (CNI) plugin for Kubernetes pod-network connectivity. The company must expose the application to the internet by using a Network Load Balancer (NLB).

The pods that host the application must be able to see the source IP address contained in the original packet received by the NLB.

How should the network engineer configure the NLB and Amazon EKS settings to meet these requirements?

  • A Specify the ip target type for the NLB. Set the externalTrafficPolicy attribute to Local in the Kubernetes service specification.
  • B Specify the instance target type for the NLSet the externalTrafficPolicy attribute to Cluster in the Kubernetes service specification.
  • C Specify the instance target type for the NLB. Set the externalTrafficPolicy attribute to Local in the Kubernetes service specification.
  • D Specify the ip target type for the NLB. Set the externalTrafficPolicy attribute to Cluster in the Kubernetes service specification.
Explanation

An NLB with the ip target type routes traffic directly to pod IP addresses, which are routable through the Amazon VPC CNI. externalTrafficPolicy: Local preserves the external client source IP by avoiding cross-node forwarding and the associated source NAT for the Kubernetes Service. AWS documents that IP targets route directly to pods and that externalTrafficPolicy=Local supports client source-IP preservation.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!