Kubectl Cheat Sheet

Core Philosophy

1. Optimize for the command you need right now — Cheat sheets should get you to the right command quickly, not explain Kubernetes from first principles.
2. Group by operational task, not alphabetically — Operators think in “inspect pods” and “roll out a deployment,” not in raw verb order.
3. Prefer safe read commands first — get, describe, logs, and diff should come before write actions when debugging.
4. Make selectors and namespaces explicit — Most kubectl mistakes come from targeting the wrong objects or cluster scope.
5. Include output shaping — -o wide, -o yaml, jsonpath, and label selectors often matter as much as the base command.

Quick-Start: Common Problems

"What pods are broken right now?"

1. kubectl get pods -A
2. kubectl describe pod <pod> -n <ns>
3. kubectl logs <pod> -n <ns> --previous -> See references/commands.md