Every api Pod shows 0/1 Running. The containers run fine, but the readiness probe fails, so the Pods stay out of the Service's endpoints.
About this scenario
Every api Pod shows 0/1 Running. The containers run fine, but the readiness probe fails, so the Pods stay out of the Service's endpoints.
Find what the probe checks and what the app actually serves.
Objectives
- Find the failing probe in the events
- All 3 api Pods are Ready
- The api Service has 3 endpoints
What you'll practice
- Readiness decides whether a Pod gets traffic. A failing readiness probe never restarts the container; a failing liveness probe does.
- A probe can name a port by its name, which keeps it in step with the container's ports.
- Changing the probe is a template change, so it rolls out new Pods.
How the playground works
The cluster runs entirely in your browser: a simulated API server, scheduler, kubelets and controllers, with virtual nodes in three zones. kubectl output follows the real formats, errors use the real messages, and the add-ons (CSI storage, Traefik, Envoy Gateway, cert-manager, Flux, Argo CD) behave like their real counterparts for the common paths. It's a simulation, so some behavior is simplified. Your progress is saved in this browser.