15 articles tagged with Operations.
Teams spend most of their Kubernetes time debugging, not building. This is the map to the errors that eat that time: what each one means, how to diagnose it fast, and the fix.
The ordered kubectl toolkit we reach for when a pod misbehaves, with the five commands we run first and what each one actually tells you.
A pod that logged fine for weeks starts throwing EMFILE at 3am. Here's how to tell a real file-descriptor leak from a limit that's just set too low.
A node flips to NotReady and pods start disappearing. Here's the order we check things in, the usual culprits, and how to recover without making it worse.
A PVC stuck in Pending means nothing on the cluster can hand it a volume. Here's how we read the events and get it bound fast.
Your pods are running, your Service exists, and nothing can reach it. Here's the exact order we check things when a Kubernetes Service goes dark.
A pod stuck in CreateContainerConfigError means kubelet can't build the container config, almost always a ConfigMap or Secret reference that doesn't line up.
Every crash loop leaves a number behind. Learn to read exit codes straight from kubectl describe and know the fix before you open the logs.
A pod sits Pending and the scheduler quietly logs why it rejected every node. Learn to read that one line and fix the real cause instead of guessing.
Evicted pods are the kubelet telling you a node ran out of something. Here's how to read the signal, stop the bleeding, and keep it from happening again.
A Pending pod means the scheduler couldn't place it or the node couldn't start it. Here's how to read the events and clear the eight causes we hit most.
A pod dies, restarts, dies again, and the events say OOMKilled. Here is what exit code 137 actually means and how to stop the loop for good.
