DevOps Practitioner · Module 1: Kubernetes workload management · Lab
Fix Traffic Cut by a Wrong Probe
45 min hands-on · Core
A local KinD or k3d cluster on a machine you own, with the demo service exposing /alive and /ready paths.
Local guide: run the steps below on your own machine in order, then check the validation list.
Objectives
- Show a readiness probe sending traffic to a cold pod
- Rewire readiness to the true ready path with warmup cover
- Prove the Service waits before adding the pod to endpoints
Step 1
Wire the lying probe
Set readiness to the /alive path that answers instantly. Roll the Deployment and capture requests hitting a pod whose /ready path still reports cold. Save the cold-traffic evidence.
Step 2
Probe the true path
Point readiness at /ready, which checks the fixture store, and add a startup probe covering the measured warmup. Roll again and show endpoints staying empty until the pod reports ready.
Step 3
Record the before and after
Keep both probe definitions and the endpoint observations side by side: traffic-during-warmup before, clean wait after. State the rule the repair follows.
How to confirm it worked
- Cold-traffic evidence captured with the lying probe
- Corrected probe checks the dependency path with warmup covered
- Endpoints observed empty until ready, shown in the record
- Both probe definitions kept with the stated rule