kubernetes-troubleshootinglisted

# Kubernetes Troubleshooting Take a workload from "it is not working" to a named root cause, using the pod lifecycle as the search order. ## Purpose **Use this when:** - A pod is in `CrashLoopBackOff`, `Pending`, `ImagePullBackOff`, `ErrImagePull`, `Init:Error`, `CreateContainerConfigError`, `Evicted`, or stuck `Terminating`. - A `kubectl rollout status` never completes. - A workload reports `Running` but `READY 0/1`. **Do not use this when:** - Pods are healthy and the problem is traffic not reaching them — use `kubernetes-networking`. - The question is "is this workload production-ready?" — use `kubernetes-production-readiness`. - The cluster itself is degraded (API server unreachable, all nodes `NotReady`) — that is a cluster incident; start with `incident-triage`. **What this skill assumes:** a working kubeconfig with at least read access to the namespace, and `kubectl` on the path. ## Operating Procedure 1. **Establish context.** Confirm which cluster and namespace you are in before running anything else. Getting this wrong is the single most common cause of a wasted investigation — and of changing the wrong environment. 2. **Classify the phase.** Pod status maps to a layer: `Pending` is the scheduler, `ImagePull*` is the kubelet or registry, `CrashLoopBackOff` is the container, `Running 0/1` is the probe or the application. Search only that layer first. 3. **Read events before logs.** Events explain why Kubernetes did or did not do something. Lo