View a markdown version of this page

Expose Amazon EKS Microservices in IPv6 Clusters - Expose Microservices Using Amazon EKS

Expose Amazon EKS Microservices in IPv6 Clusters

This architecture shows how to expose Amazon EKS microservices with IPv6 and connect to both IPv6 and IPv4 endpoints on the internet. Moving to IPv6 also solves pod IP exhaustion because you do not need to work around IPv4 limits.

Expose Amazon EKS Microservices in IPv6 Clusters

Architecture diagram showing Amazon EKS microservices in IPv6 clusters with dual-stack load balancers and egress-only internet gateway.

The following steps describe the inbound flow:

  1. Amazon Route 53 resolves incoming requests to the public ELBs in dual-stack mode deployed by the AWS Load Balancer Controller.

  2. The ELB forwards traffic to the IPv6 pods using IP mode.

The following steps describe the outbound IPv6 flow:

  1. Any pod communication from within private subnets to IPv6 endpoints outside the cluster routes through an egress-only internet gateway (EIGW).

The following steps describe the outbound IPv4 flow:

  1. A pod in a private subnet initiates an outbound request to an IPv4 address on the internet and performs a DNS lookup. Upon receiving an IPv4 "A" response, the pod establishes a connection using the IPv4 address from the host-local 169.254.172.0/22 IP range.

  2. The pod's node-only unique IPv4 address is translated through NAT to the IPv4 (VPC) address of the primary network interface attached to the node.

  3. The private route table forwards traffic to the NAT gateway, and the private IPv4 address of a node is translated to the public IPv4 address of the gateway.

Note

At the time of this writing, ALB and NLB support dual-stack for only internet-facing endpoints. Amazon EKS implements a host-local CNI plugin chained along with VPC CNI to allocate and configure an IPv4 address for a pod from the 169.254.172.0/22 range.

Further reading

For additional information, refer to the following resources:

Diagram history

To be notified about updates to this reference architecture diagram, subscribe to the RSS feed.

ChangeDescriptionDate

Initial publication

Reference architecture diagram first published.

February 22, 2022

Initial publication

Reference architecture diagram first published.

February 22, 2022

Initial publication

Reference architecture diagram first published.

February 22, 2022

Note

To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.