AWS › Amazon EKS (Elastic Kubernetes Service)

How does Kubernetes networking work within an EKS cluster using the Amazon VPC CNI plugin?

Intermediate

Answer

The Amazon VPC Container Network Interface plugin assigns each Kubernetes pod its own real IP address directly from your VPC's IP address range, meaning pods can communicate with other AWS resources and be reached using standard VPC networking and security groups, unlike some other Kubernetes networking setups that rely on an overlay network requiring extra translation layers.
kubectl get pods -o wide
Real-world example A team troubleshooting network connectivity issues in their EKS cluster can directly apply familiar VPC security group rules and flow logs to their pods, since each pod has a real, routable VPC IP address rather than an isolated overlay address.

Common follow-ups: What happens if a subnet runs out of available IP addresses for pods?;How does the VPC CNI plugin compare to other Kubernetes networking plugins?