kubectl Cheatsheet 2026

Top 30 commands.

Overview

The kubectl 2026 cheatsheet captures the patterns operators actually use during Kubernetes investigation. Knowing every flag matters less than fluency under pressure; the canonical 30-command set covers most of incident-response use.

• Top 30 commands. Per-resource get/describe/logs/exec; the four verbs that resolve most investigations.
• kubectl get -o wide. Wide output for investigation; surfaces node placement and IPs the default view hides.
• kubectl logs -f --tail=100. Per-pod live tail; the canonical debug path for "what is this pod doing right now?"
• kubectl exec -it plus kubectl debug. Shell into pod for investigation; ephemeral debug containers for distroless or scratch images.

The approach

The practical approach: alias the high-frequency commands, prefer jq-friendly output, install kubecolor, use kubectx/kubens for context, document team conventions. The team’s discipline produces fast operations under incident pressure.

• Alias everything. k for kubectl, kgp for get pods; matches the frequency of use.
• jq-friendly output. -o jsonpath and -o json; supports automation and shell-pipeline integration.
• kubecolor for readability. Per-team kubecolor install; the colour cues speed visual scanning under pressure.
• Per-context awareness plus documented patterns. kubectx and kubens for multi-cluster; per-team kubectl conventions documented for adoption.

Why this compounds

kubectl fluency compounds across investigations. Each captured pattern grows the team’s K8s operations; the next investigation starts from precedent.

• Faster operations. Fluent kubectl produces fast results; the operator runs the command, not the syntax lookup.
• Better investigation. Right command produces fast root cause; reduces MTTR by replacing speculation with kubectl output.
• Better automation. kubectl in scripts produces reproducible operations; one-off becomes runbook.
• Institutional knowledge. Each command teaches K8s patterns; the team’s K8s muscle grows.

kubectl fluency is an operational discipline that pays off across years. Nova AI Ops integrates with K8s telemetry, surfaces patterns, and supports the team’s K8s discipline.