kubectl debug: Ephemeral Containers Changed How I Troubleshoot
kubectl debug with ephemeral containers fixes the oldest problem in Kubernetes troubleshooting: distroless images with no shell. Distroless and node debugging.
Read the postPosts tagged "debugging"
6 posts about debugging in the conndeck blog — field notes on local-first Kubernetes operations, GitOps, and production debugging.
ImagePullBackOff: Every Cause I've Actually Hit
ImagePullBackOff has four real causes: bad tags, registry auth, rate limits, and network. Learn to read the pull error and fix the right one.
Read the postOOMKilled: Debugging Memory Limits Without Guessing
OOMKilled and exit code 137 mean the kernel killed your container. Learn to read Last State, separate cgroup OOM kills from eviction, and find the actual leak.
Read the postYour Pod Is Stuck in Pending: The Actual Checklist
Pod stuck in Pending? Run the real checklist: kubectl describe events, 0/N nodes available reasons, taints and tolerations, resource requests, and unbound PVCs.
Read the postForbidden: Debugging RBAC Without Handing Out cluster-admin
RBAC Forbidden errors decode completely if you read them. Use kubectl auth can-i, impersonation, and bindings to grant exactly what's missing.
Read the postCrashLoopBackOff: A Field Guide From Someone Who's Been There
CrashLoopBackOff isn't one error, it's five. A practical debugging guide to restart counts, last state, logs --previous, and the causes I actually see in production.
Read the post