kubectl as an API Client

kubectl is a thin API client. Context selects cluster, user and namespace; discovery finds resource types; get retrieves collections; describe combines object details and related events; apply patches declared intent. Use kubectl explain, --dry-run=client -o yaml, JSONPath and -o wide to work quickly without guessing fields. Always verify current-context and namespace before mutation.

Analogy: Kubernetes is a thermostat, not a remote control. You declare the temperature; independent controllers measure reality and keep acting. Debugging means finding which sensor, rule or actuator prevents convergence.

Read the object as evidence

kubectl get RESOURCE NAME -n NAMESPACE -o yaml
kubectl describe RESOURCE NAME -n NAMESPACE
kubectl get events -n NAMESPACE --sort-by=.metadata.creationTimestamp
kubectl explain RESOURCE.spec

Do not memorize these as a ritual. The first command exposes desired and observed state, the second connects conditions and events, the third supplies a timeline, and the fourth checks the server's schema. Compare what the controller was asked to do with what it reports doing. Then test the narrowest hypothesis.

Scenario: A correct command aimed at the wrong context is still an outage. Production practice makes target verification part of the command, uses explicit namespaces for risky changes, and captures before/after state.

Build a safe kubectl habit

Start risky sessions with kubectl config current-context, kubectl config view --minify, and an explicit -n. Prefer kubectl diff -f before apply; use --dry-run=server when admission and server defaults matter. For repeatable inspection, select columns deliberately: kubectl get pods -o custom-columns='NAME:.metadata.name,NODE:.spec.nodeName,READY:.status.containerStatuses[*].ready'. Save the original YAML before an emergency patch and verify generation, rollout status and the user path afterward.

Scenario: A manifest passes client-side dry-run but production admission rejects it. Client validation knew the schema it shipped with; server dry-run exercises the actual API version, policies and webhooks.
Warning: Shell aliases that hide context or namespace save keystrokes but increase ambiguity during incidents. Commands copied into a timeline should reveal their target.

Production reasoning

Ask four questions: Who owns this object? What dependency must become ready next? Which controller reports the blocking condition? What evidence would disprove my current theory? This prevents symptom-driven changes. Record the context, namespace, object generation, image digest and recent rollout before mutation; a recreated Pod may erase the evidence you needed.

Warning: Running is not the same as ready, healthy, durable or correct. Kubernetes status is layered. Confirm the application-level outcome as well as the object state.
Goal: Put this model into practice in the Kubernetes lab namespace-basics. Open /labs/kubernetes, choose namespace-basics, predict the failure path before changing anything, then use the simulator's check command to validate the finished state.

Deliberate practice

Before the lab, write the expected object relationship and the first three commands you will run. Afterward, explain why the fix converged and name one tempting change that would only mask the symptom. Repeat using an explicit namespace and a structured output format. This prediction-observation-explanation loop is what turns command familiarity into production judgment.

45-minute investigation

  1. Map (5 min): draw the owner-to-child chain and mark every namespace, selector, identity and dependency involved.
  2. Predict (5 min): write one expected status condition, one likely event and one log or metric signal before opening the lab.
  3. Observe (10 min): collect YAML, describe output and ordered events. Do not mutate state. Record which observation disproves your first theory.
  4. Repair (15 min): make the smallest declarative correction, watch the responsible controller converge, and verify the user-facing path rather than stopping at Running.
  5. Stress (10 min): change one relevant constraint - replica count, label, readiness, resource value or placement rule - predict the outcome, observe it, then restore the known-good declaration.
Tip: Keep a short incident note with symptom, evidence, hypothesis, change, result. Across four sections this produces a reusable runbook instead of a pile of remembered commands.