Payments service, mission 3 of 4
No shell
advanced, about 15 minutes, in the Kubernetes Simulator
Opens once you pass Not dead, just slow.
The briefing
From Dana Kowalski, on-call lead at Larchwood (a fictional company)
Platform is moving the payments database this morning. If payments stops being ready, the logs won't help much — they only say upstream database unavailable.
And the image is distroless: there's no shell to kubectl exec into. kubectl debug adds a temporary container with tools to a running pod, sharing its network. Find out what payments can't reach, and fix it.
What you'll do
- payments: 2 ready replicas
- payments reaches its database by a name that resolves
- Bonus star: Look from inside with kubectl debug before changing anything
The mission checks the cluster, not your keystrokes: any fix that works, passes.
Concepts
kubectl debug
Adds an ephemeral container to a running pod: same network, and with
Read the Kubernetes docs--targetthe same process view, but your choice of image — busybox has nslookup and wget. Without-it, it runs one command;kubectl logs POD -creads its output. It can't be removed, and it never changes the app's container.