Answer-first summary for fast verification
Answer: Check the pending pod `helloworld-deployment-a1b2c3-lp88c` for warning messages.
Option A is incorrect because inspecting the service won't help as the failing resource is the pod. Option B is incorrect because the deployment won't display error messages; the pods will. Option C is correct because the failing pod will show warning or error messages indicating why it's failing. Option D is incorrect because logs won't be available for a failed container. For more information, refer to [Google Cloud's troubleshooting guide](https://cloud.google.com/run/docs/gke/troubleshooting) and [Kubernetes debugging documentation](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/#debugging-pods). Additionally, Cloud Logging offers real-time log management and analysis, providing insights into application and platform log data across various environments.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
As part of a pilot project for implementing Kubernetes at your logistics startup, your team is experimenting with various Kubernetes YAML configurations for a test app. After executing the command kubectl get pods -l app=helloworld, you notice one of the pods remains in a PENDING state. You're tasked with debugging the issue. What should you do?
A
Examine the helloworld-service Service object for error messages.
B
Review the helloworld-deployment Deployment object for error messages.
C
Check the pending pod helloworld-deployment-a1b2c3-lp88c for warning messages.
D
Inspect the logs of the container in the pending pod helloworld-deployment-a1b2c3-lp88c for warning messages.
No comments yet.