How do you troubleshoot common Kubernetes pod failures and container issues?

Troubleshooting Kubernetes pod failures requires systematic analysis of pod lifecycle, events, and logs to identify root causes.\n\nCommon Pod Failure Scenarios:\n• ImagePullBackOff: Cannot pull container image\n• CrashLoopBackOff: Container keeps crashing\n• Pending: Pod cannot be scheduled\n• OOMKilled: Out of memory errors\n• Init container failures\n\nTroubleshooting Steps:\n1. Check pod status: kubectl get pods\n2. Describe pod: kubectl describe pod \n3. Check logs: kubectl logs -c \n4. Check events: kubectl get events\n5. Verify resources and limits\n\nExample Commands:\nkubectl describe pod failing-pod\nkubectl logs failing-pod --previous\nkubectl get events --sort-by=.metadata.creationTimestamp\n\nBest Practices:\n• Monitor resource usage continuously\n• Implement proper health checks\n• Use structured logging\n• Set appropriate resource limits\n• Regular cluster maintenance