REST API, mission 4 of 7
Ready when it's ready
intermediate, about 10 minutes, in the Kubernetes Simulator
Start mission
Opens once you pass CrashLoopBackOff.
The briefing
Checkout is timing out. The orders pods are Running, nothing is crashing — and yet the orders Service sends traffic nowhere.
A readiness probe is how a pod tells Kubernetes it can take traffic. Until it passes, the pod is kept out of every Service's endpoints. orders-api answers two health paths: /healthz (the process is alive) and /ready (it can reach its database).
What you'll do
- Work out why the Service has no endpoints
- The orders Service routes to 2 ready pods
- Bonus star: Also give the pods a liveness probe on /healthz
The mission checks the cluster, not your keystrokes: any fix that works, passes.
Read first
More REST API missions
- 1. Config, not code
- 2. Read at start
- 3. CrashLoopBackOff
- 4. Ready when it's ready
- 5. Out of memory
- 6. Launch-day traffic
- 7. Rotate the password