Answer-first summary for fast verification
Answer: Review the details of the pending Pod object for any warning messages that might explain the status.
The correct answer is to review the details of the pending Pod object for any warning messages. This approach is most effective because the issue is specific to a single pod's status. Common causes for a pod remaining in PENDING status include insufficient resources on the Kubernetes nodes, such as CPU or memory. Describing the pod will provide detailed information about such warnings or errors, guiding you towards the appropriate resolution, such as enabling auto-scaling or manually scaling up the nodes. Other options, such as checking the Service or Deployment objects, or inspecting container logs, are less likely to reveal the root cause since the pod has not yet started running, making its logs inaccessible, and the issue is not with the deployment or service configuration.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
After deploying a new application in your Google Kubernetes Engine cluster using the provided YAML file, you notice one of the pods remains in a PENDING status. The other pod is running successfully. What is the best course of action to diagnose why the pod is stuck in pending status?
A
Inspect the logs of the container within the pending pod for any warning messages.
B
Examine the details of the Service object for any error messages related to the pending pod.
C
Describe the Deployment object to check for any error messages affecting the pod.
D
Review the details of the pending Pod object for any warning messages that might explain the status.
No comments yet.