ngaxavi

kubernetes-troubleshooting

Systematic triage of failing Kubernetes workloads using kubectl. Use when a pod is Pending, CrashLoopBackOff, ImagePullBackOff, OOMKilled, Error, or stuck Terminating; when a PersistentVolumeClaim will not bind; when a Service returns no endpoints or connections are refused; when an app is reachable inside the cluster but not from outside via Ingress or the Gateway API; when a Deployment's replicas never appear because a ResourceQuota, LimitRange, Pod Security, or admission webhook rejected them; when DNS resolution fails inside the cluster; or when a node is NotReady or reporting disk, memory, or PID pressure. Use when a Secret or config is missing or a live change keeps reverting (operator-synced secrets, GitOps reconciliation). Use when someone asks why a workload is not running, not reachable, or not scheduling. Use it too for proactive health checks — when someone asks "is the cluster OK?" or whether something is healthy even though nothing is obviously failing, since a green-looking cluster can still hi