kubectlBeginnerPod DebuggingDecision Trainer

5 kubectl Commands Every Kubernetes Beginner Should Know

Start with get, describe, logs, exec, and apply — then practice choosing the right one first in realistic scenarios, not just memorizing syntax.

2026-06-071 min read

Most Kubernetes tutorials jump straight to YAML. That is backwards for day one.

Before you can debug a CrashLoopBackOff or unstick a rollout, you need a small set of kubectl verbs in muscle memory. These five show up on almost every shift — and on CKAD/CKA-style troubleshooting tasks:

kubectl get pods
kubectl describe pod <name>
kubectl logs <pod>
kubectl exec -it <pod> -- sh
kubectl apply -f manifest.yaml

Why "knowing the command" is not enough

Reading a command once does not help when a pod is red at 2 a.m. — or minute 47 of an exam.

What matters is which command you reach for first:

Pending → describe pod (scheduling Events), not logs
CrashLoopBackOff → logs --previous, often after a quick describe
Service unreachable → get endpoints / EndpointSlices, then trace to pods

That is what Decision Trainer practices: scenario context, four plausible next steps, graded feedback.

Try Pod Debugging free

Our Pod Debugging path is free — scenario cases with terminal-style context and a debrief on your first-step choice. No account required for a session.

When you are ready, unlock operational paths (Services, rollouts, scheduling, storage…) for $9.99 each, or Decision Trainer Pro for $29.99 (all seven core topics). CKAD ($19.99) and CKA ($24.99) exam prep packs are separate — 100 scenarios each for certification-specific practice.

Next: If Pending pods confuse you, read Pending Pods: When Kubernetes Has Nowhere to Run — then drill the Scheduling topic.