Define what a Kubernetes Pod is, explaining its fundamental purpose and characteristics (e.g., smallest deployable unit, ephemeral nature, shared resources within a pod). How does the concept of a Pod relate to the crashing application in the given scenario? What specific information would you look for within a Pod to diagnose the crash?

Explain what a Kubernetes Deployment is and its primary function, particularly in managing stateless applications. Elaborate on how a Deployment uses ReplicaSets to maintain the 'desired state.' What mechanisms does it employ to ensure the specified number of healthy pods are always running? In the context of the crashing pod scenario, how does the Deployment's behavior (e.g., restarting a crashing pod) become part of the problem, and how might you use Deployment-related commands to gather diagnostic information or intervene?

Describe what a Kubernetes Service is and its role in enabling network access to a set of Pods. Explain how a Service provides a stable network endpoint, even when underlying Pods are created, destroyed, or moved. Discuss the different types of Services (e.g., ClusterIP, NodePort, LoadBalancer) and their use cases. While a Service itself might not be directly causing the pod crash, how does its interaction with the continually crashing Pod affect application availability? What role does a Service play in observing the application's external behavior during this debugging process?

Summarize how Pods, Deployments, and Services collectively contribute to the operational state of an application in Kubernetes. Based on the scenario of a crashing pod, outline a high-level debugging strategy utilizing your understanding of these three components, detailing the steps you would take to identify the root cause.