Cheapest-Next-Test Boundaries in Kubernetes
Learn to troubleshoot Kubernetes 502 errors by following the request path from Service wiring to application behavior. Use cheapest-next tests to evaluate selectors, EndpointSlices, readiness, DNS, reachability, and logs, while stating falsifiable expectations and verifying reversible fixes.
We'll cover the following...
A 502 with Pods shown as Running creates a costly temptation to read application logs first. In an interview, the stronger approach is to test the cheapest boundary that can rule out the broadest hypothesis. Running only confirms that a container has started; it does not establish that a Service selects it, that it is ready to receive traffic, or that another workload can reach it.
Boundary-first troubleshooting follows the request path, starting with cluster wiring and moving toward application behavior. A boundary is where one component hands work to another, and where we can collect observable ...