Kubernetes troubleshooting

Kubernetes Pod Pending: Diagnosing 7 Causes with kubectl describe

When a Pod is stuck in Pending and causing a service outage, stop guessing. This practical guide use…

Solving CrashLoopBackOff: Diagnosing 7 Causes of Infinite Pod Restarts

If a Pod keeps restarting with CrashLoopBackOff, narrow the cause in a minute with kubectl describe …

Diagnose and Fix Pod Evicted "node was low on resource" in 5 Minutes

If a Pod is Evicted with a "node was low on resource" error, the culprit is the node's DiskPressure …

When a Kubernetes Pod Gets Stuck in Terminating: 5 Causes and Safe Force Deletion

When a Kubernetes Pod is stuck in Terminating and will not delete, diagnose five causes—ignored SIGT…

6 Major Causes of Liveness/Readiness Probe Failures and How to Fix Them: Stopping Infinite Pod Restarts

If the app is healthy but the Pod restarts with CrashLoopBackOff or returns 503s, the cause is usual…

Kubernetes Pod DNS Failure (CoreDNS) 5-Minute Diagnosis: can't resolve & Temporary failure

Classify Kubernetes Pod DNS failures—nslookup can't resolve and Temporary failure in name resolution…

kubectl get nodes NotReady: Diagnose 6 Causes and Recover in 5 Minutes

If a worker node goes NotReady and every Pod dies, branch on six causes—kubelet down, CNI plugin not…

Kubernetes PVC Stuck in Pending: 6 Causes and a 5-Minute Diagnostic Guide

Is kubectl get pvc stuck on Pending and your Pod frozen at ContainerCreating? Pin down which of the …

6 Ways to Fix kubectl Unauthorized (You must be logged in) 401

Fix the kubectl "You must be logged in to the server (Unauthorized)" 401 error in five minutes with …

Fix ImagePullBackOff · ErrImagePull: Diagnose the Cause from Events and Finish with Copy-Paste

Pinpoint kubectl ImagePullBackOff and ErrImagePull in five minutes with an Events-message diagnosis …

Fixing OOMKilled Exit Code 137: A kubectl 30-Second Diagnosis and 5-Minute Recovery Runbook

Did your Pod die with OOMKilled exit code 137? In 30 seconds, use kubectl describe, jsonpath, and dm…

Pod Pending FailedScheduling 0/3 nodes: A 30-Second Diagnosis and Recovery Runbook

Is your Pod stuck in Pending with FailedScheduling 0/3 nodes (insufficient cpu/memory, taint, or nod…

K8s Liveness/Readiness Probe Failed · Connection Refused: Fixes by Cause

Match the exact Liveness/Readiness probe failed, connection refused, and context deadline exceeded s…

kubectl localhost:8080 refused: a 30-second diagnosis and recovery runbook

Fix kubectl's "connection to localhost:8080 was refused" error with a 30-second diagnostic table and…