You deployed an app to GKE and one pod remains in PENDING. How should you determine why the pod is pending?

When a pod is in a PENDING state, it means the Kubernetes scheduler has not yet assigned it to a node, or it's in the process of being pulled. To understand why, you need to inspect the specific pod's events. The command kubectl describe pod myapp-deployment-58ddbbb995-lp86m will show detailed information about the pod, including events, which often contain warning messages indicating issues like insufficient resources (CPU, memory), node taints/tolerations, or persistent volume claims not being met. Reviewing the Service object (myapp-service) is incorrect because a Service defines how to access a set of pods, not the state of individual pods. Reviewing the Deployment object (myapp-deployment) is also incorrect; while a Deployment manages the desired state of pods, it doesn't directly show why a specific pod is pending. Viewing container logs is incorrect because a pod in PENDING state means its containers haven't started yet, so there would be no logs to view.