Interview AWS

How does the AWS VPC CNI assign pod networking on EKS?

AWS · Intermediate level

Answer

The AWS VPC CNI gives pods routable VPC IPs by assigning ENI secondary IPs or prefixes from subnets to nodes. This makes pod-to-VPC communication simple but turns subnet IP capacity and ENI limits into scaling concerns.

Technical explanation

Subnet IP exhaustion is a common EKS scaling failure mode when using the VPC CNI.

EKS is managed Kubernetes, not no-ops Kubernetes: IAM, networking, add-ons, node strategy, upgrades, RBAC, policies, and workload reliability remain customer responsibilities.

Workload identity, private networking, image security, ingress standards, autoscaling, and observability are foundational controls for production clusters.

Troubleshooting EKS requires separating control-plane, node, CNI, scheduler, ingress, and application failure domains.

Hands-on example

1. Create or use an EKS sandbox cluster with private subnets, managed add-ons, workload IAM, and a sample namespace.

2. Deploy a small container from ECR using Kubernetes manifests or Helm, with readiness/liveness probes and resource requests.

3. Add ingress/load balancing, pod IAM, logging, metrics, and network/security controls relevant to the question.

4. Test node replacement, pod rescheduling, image pulls, access control, and rollback.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More AWS interview questions

← All AWS questions