This post is the third installment in a series on the Kubernetes API, focusing on diagnosing why a Pod might not be getting traffic in a Kubernetes deployment and introducing the diagnostic tool kubespy. It provides an insightful exploration of common issues such as service existence, Pod readiness, DNS reachability, and kube-proxy functionality, which can affect the flow of traffic to a Pod. The post highlights the functionality of the kubespy trace command, which automates the process of checking certain key factors in real time, offering a clear view of a Service's lifecycle from creation to public exposure. The tool, derived from Kubernetes support developed for Pulumi, aims to simplify the deployment of applications on Kubernetes by providing concise, real-time insights into resource statuses. The post encourages experimenting with different service types and observing the effects of deployment changes, while hinting at future expansions of the tool's capabilities to cover more aspects of app rollouts.