1Z0-1084-20 · Question #17
1Z0-1084-20 Question #17: Real Exam Question with Answer & Explanation
The correct answer is B. kubect2 describe pod nginx. The first step in debugging a pod is taking a look at it. Check the current state of the pod and recent events with the following command: kubectl describe pods ${POD_NAME} Look at the state of the containers in the pod. Are they all Running? Have there been recent restarts? Cont
Question
Options
- Akubect2 logs pod nginx
- Bkubect2 describe pod nginx
- Ckubect2 get pod nginx
- DThrough the Oracle Cloud Infrastructure Console
Explanation
The first step in debugging a pod is taking a look at it. Check the current state of the pod and recent events with the following command: kubectl describe pods ${POD_NAME} Look at the state of the containers in the pod. Are they all Running? Have there been recent restarts? Continue debugging depending on the state of the pods. My pod stays pending If a pod is stuck in Pending it means that it can not be scheduled onto a node. Generally this is because there are insufficient resources of one type or another that prevent scheduling. Look at the output of the kubectl describe ... command above. There should be messages from the scheduler about why it can not schedule your pod. https://kubernetes.io/docs/tasks/debug-application-cluster/debug-pod-replication-controller/
Community Discussion
No community discussion yet for this question.