~/ nmadiraju.com Amazon EKS · How Ingress works
arrow_back Back to nmadiraju
Visual Walkthrough · Amazon EKS networking

How Ingress Works on Amazon EKS

Follow one request for shop from inside the cluster to the internet, then check yourself with 8 questions.

1Visual Walkthrough

One EKS cluster, built up step by step, with a packet tracing each request The geometry never changes. Each step adds the objects it introduces: a Service and kube-proxy, then a NodePort, an NLB per Service, an Ingress, and the AWS Load Balancer Controller that builds one ALB. A packet travels each step's path, and its destination label changes where kube-proxy or a load balancer rewrites it. Client laptop · internet VPC · 10.0.0.0/16 PUBLIC SUBNETS PRIVATE SUBNETS · pods get VPC IPs node-1 · EC2 · 10.0.1.10 node-2 · EC2 · 10.0.2.10 kube-proxy node rules kube-proxy node rules web pod 10.0.1.22 calls shop shop-7d9f-a 10.0.1.15 app=shop · :8080 api-5c8b-a 10.0.1.31 app=api · :8080 CoreDNS kube-system answers *.svc names shop-7d9f-b 10.0.2.31 app=shop · :8080 api-5c8b-b 10.0.2.44 app=api · :8080 LB Controller kube-system watches Ingress NLB · shop TCP :80 1 per Service REMOVED NLB · api TCP :80 another DNS name REMOVED ALB HTTP :80 /api → api / → shop :30080 :30080 KUBERNETES API · EKS Service shop ClusterIP 172.20.14.7 Pods 10.0.1.47, 10.0.2.31 Service api ClusterIP 172.20.9.3 Ingress shop /api → api:80 / → shop:80 ADDRESS: (empty)

    2Quiz to check understanding

    Check yourself