Meet kubectl
The remote control for your cluster.
In plain terms
kubectl is the TV remote for your cluster: you press buttons (commands) from the couch and things happen across the room. You never get up and touch the TV itself.
kubectl (say “kube-control” or “kube-cuttle” — everyone argues) is how you talk to a cluster. Every command is a polite request to the control plane’s front door. You run it from your own machine; the cluster does the work.
The five commands of day one
You can go a long way with just five: get (list things), describe (full details plus recent events), apply (create or update from a file), logs (see a container’s output), and exec (open a shell inside a container). describe is the one beginners forget — it is where Kubernetes tells you why something is stuck.
terminal
$ kubectl get nodes # the machines in the cluster$ kubectl get pods -A # every running pod, all namespaces$ kubectl get pods -o wide # add the node and IP columns$ kubectl describe pod web-xyz # full details + recent events$ kubectl logs web-xyz # what the container printed
Stuck? describe first
When something is not working, kubectl describe is almost always the fastest answer — the “Events” at the bottom explain the why in plain English before you ever open logs.