Explanation:
The correct answer is C: Review details of myapp-deployment-58ddbbb995-lp86m Pod and check for warning messages. To diagnose why a pod is stuck in a PENDING state, you need to review the specific details and warning messages related to that pod. Using the kubectl describe pod <pod-name> command allows you to gather detailed information which might indicate the issue, such as insufficient resources or configuration errors.
Ultimate access to all questions.
No comments yet.
You have recently deployed a new application within your Google Kubernetes Engine (GKE) cluster utilizing the provided YAML file. Upon checking the status of the deployed pods, you observe that one of them remains in a PENDING state. You aim to diagnose the cause of this pod being stuck in the pending status. What steps should you take to investigate and resolve this issue?
A
Review details of the myapp-service Service object and check for error messages.
B
Review details of the myapp-deployment Deployment object and check for error messages.
C
Review details of myapp-deployment-58ddbbb995-lp86m Pod and check for warning messages.
D
View logs of the container in myapp-deployment-58ddbbb995-lp86m pod and check for warning messages.