~/ nmadiraju.com Amazon EKS · Pods
arrow_back Back to nmadiraju
Visual Walkthrough · Kubernetes fundamentals

How Pods Work on Amazon EKS

Follow one Pod through a crash and a replacement, see what stays and what changes, then check yourself with 8 questions.

1Visual Walkthrough

One Pod with two containers on an EKS node, followed through a crash and a replacement A Pod on node-1 holds an app container and a log-shipper container that share one IP and an emptyDir volume. The walkthrough shows localhost between containers, a shared log file shipped to CloudWatch Logs, a container restarted in place with the same IP, the Pod replaced on node-2 with a new IP and reached through a Service, the database moved to its own Pod, and an init container that waits for it. Caller another Pod node-1 · EC2 · 10.0.1.10 kubelet starts and restarts containers Pod web-7d9f8-k2xqp IP 10.0.1.15 POD DELETED app container listens on :8080 image web:1.4 log shipper container listens on :2020 image fluent-bit shared network · one IP 10.0.1.15 · reach each other on localhost emptyDir volume, mounted in both at /var/log holds app.log init container wait-for-db runs first, must succeed database container postgres in the web Pod node-2 · EC2 · 10.0.2.10 web-7d9f8-x9k2q IP 10.0.2.47 new Pod · new name · new IP Service web stable name follows the Pods Pod postgres-0 its own Pod scales on its own can't see /var/log/app.log can't reach the database CloudWatch Logs where the shipper sends logs

    2Quiz to check understanding

    Check yourself