Improvement for k8s.io/docs/tasks/debug/debug-application/determine-reason-pod-failure/

[harridu]

Sorry to say, but this page stops when it is getting interesting. Would it be possible to add a table of pod states and whats behind it? Here is an incomplete list:

• Init:Error
• CrashLoopBackOff
• ImagePullBackOff
• Running
• Completed
• Terminating
• Error
• others?

Having a complete list in one place would be a big improvement. Next step would be to add some guidelines for error recovery, as applicable.

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dipesh-rawat]

Page reported to issue: https://kubernetes.io/docs/tasks/debug/debug-application/determine-reason-pod-failure/
/language en

[utkarsh-singh1]

Hi @harridu, you can try -

kubectl describe pod <pod_name>

[utkarsh-singh1]

Hi @harridu, Most of the States you have mentioned are already describe in these documents, you can look at them -

• https://kubernetes.io/docs/tasks/debug/debug-application/debug-init-containers/#understanding-pod-status
• https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase
• https://kubernetes.io/docs/concepts/containers/images/#imagepullbackoff
• https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-states

[harridu]

@utkarsh-singh1 , I highly appreciate the list of links, but I wonder did you notice the "in one place" in my first comment?

[utkarsh-singh1]

@harridu noticed it, but the page you have mentioned here comes under Task section which is more practical approach to the Kubernetes concepts as compared to concepts.

[utkarsh-singh1]

Most of the errors are already described under concepts, it would be better if these links can be mentioned under What's Next.

[azn-abel]

/assign

[azn-abel]

This issue has been addressed in #44288. @harridu if this is sufficient, please close this issue

[harridu]

thank you, I highly appreciate it