Troubleshooting
2 sectionsRapid overview
Troubleshooting
TL;DR
Pod debugging follows a fixed flow: kubectl get/describe to read status and events, kubectl logs (plus --previous after a crash) to see what the container said, and kubectl exec or kubectl debug for a shell. The pod-status table — Pending, …
Read →How it works
Common Pod States: | State | Cause | Solution | |-------|-------|----------| | Pending | No node available, resource constraints | Check node capacity, resource requests | | ImagePullBackOff | Image doesn't exist, auth issues | Verify image…
Read →