Amazon Elastic Kubernetes Service (EKS) supports IPv6, enabling customers to scale containerized applications on Kubernetes
far beyond limits of private IPv4 address space, while achieving
high network bandwidth with minimal complexity.
Kubernetes uses a
flat networking model that requires each pod to receive an IP address. This simplified approach enables
low-friction porting of applications from virtual machines to containers, but requires a significant amount of IP addresses that many private IPv4 networks are not equipped to handle. Further, clusters running in IPv4 based networks require complex network routing configuration to enable pod communication with internet services.
With EKS support for IPv6, pods are assigned only a
globally routable IPv6 address, and we easily scale applications in our cluster
without consuming limited private IPv4 address space. This globally routable IPv6 address can be used to directly communicate with any IPv6 endpoint in our Amazon VPC, on-premises network, or the public internet.
IPv6 support is enabled through the
Amazon VPC CNI plugin, which directly integrates with the EC2 networking stack to deliver high performance and reliability.
With native VPC integration, we can secure our applications using standard components including
egress-only internet gateways, security groups, and network access control lists (ACL). EKS configures networking so that pods can still communicate with IPv4 based endpoints outside the cluster, enabling us to adopt the benefits of IPv6 and Kubernetes without requiring that all dependent services deployed across our organization are first migrated to IPv6.
By default, Kubernetes assigns IPv4 addresses to our pods and services. Instead of assigning IPv4 addresses to our pods and services, we can configure our cluster to assign IPv6 addresses to them. Amazon EKS doesn’t support dual-stacked pods or services. As a result,
we can't assign both IPv4 and IPv6 addresses to our pods and services.
We select which IP family we want to use for our cluster when we create it. We can’t change the family after we create the cluster.
Kindly refer the article for Assigning IPv6 addresses to pods and services – Part 2
Thanks for reading my article till end. I hope you learned something special today. If you enjoyed this article then please share to your friends and if you have suggestions or thoughts to share with me then please write in the comment box.