Access required
Kubernetes Service cannot reach pods
What the on-call engineer sees
- Pods exist and are Running, but requests to http://orders-service/api/orders fail
- Restore Service access to two ready replicas
You need an account to take this incident. Registration is free and takes a minute: just a username and password, with no email or phone number. The case you completed as a guest will carry over.
Without an account, you can complete case 0, “Store unavailable” —a short introduction in a real console.
Prepare for this caseLearn ↗
Explore the relevant skills before practice. Lessons open in a new tab.
- Kubernetes Service: Running is not Ready14 min ↗
- The request path: name, route, port, application12 min ↗
- Networking checkpoint: find the first failed contract16 min ↗