~/ nmadiraju.com Amazon EKS · Probes
arrow_back Back to nmadiraju
Visual Walkthrough · Kubernetes workloads

How Liveness, Readiness and Startup Probes Work on Amazon EKS

Follow one Pod's three probes through a slow start, an overload, a deadlock and a database outage, then check yourself with 8 questions.

1Visual Walkthrough

The kubelet probing a Pod's startup, readiness and liveness endpoints, with the Service and a database node-1 runs the kubelet and three shop Pods. shop-a shows its startupProbe, readinessProbe and livenessProbe. The Service's ready endpoints and an RDS database sit to the right. The walkthrough shows a slow app restart-looping without a startup probe, the startup probe, readiness adding and removing a Pod from traffic, liveness restarting a deadlocked container, a database-checking liveness probe restarting everything, and the timing math. node-1 · EC2 kubelet runs every probe, every periodSeconds Pod shop-a startupProbe GET /started readinessProbe GET /ready livenessProbe GET /healthz Pod shop-b same probes as shop-a Pod shop-c same probes as shop-a KUBERNETES API Service shop · ready endpoints only Ready Pods get traffic Amazon RDS · orders the database shop depends on

    Service traffic kubelet probe or action Pod or agent failing AWS resource

    Press Play to watch all eight steps, or step through with Back and Next. Red step tabs are where something breaks; green ones add the fix. Voice reads each step aloud with your browser's built-in speech.

    2Quiz to check understanding

    Check yourself