The mechanism
A Kubernetes command can target whichever context is active in kubeconfig. That context selects a cluster, user and default namespace. A correct command pointed at the wrong cluster is still wrong. Prefer an explicit approved context and namespace for every optional live example.
This edition was checked on 6 October 2026 against the official documentation, whose release page lists 1.37.1 as the latest patch. Your cluster may run another supported minor or a managed distribution. Check actual server, client and component versions before using version-sensitive behavior.
The primary path in this book is offline. Reading YAML or running the supplied standard-library fixture tests needs no cluster. A client-side dry run is not automatically network-free: discovery and validation behavior can still involve an API server. Label the scope precisely.
Worked example
These are optional read-only commands for an already approved disposable context literally named handbook-lab. Do not substitute a production context. The first command is local client information; the second inspects the current context name without displaying credentials.
kubectl version --client
kubectl config current-context
# Only after confirming the approved target exists:
kubectl --context handbook-lab -n handbook-lab get pods
# This book does not create or switch contexts.Practice: predict, inspect, explain
Offline exercise. Write a command review card with intended cluster, namespace, verb and expected effect. Compare get pods with a manifest-changing operation and a node administration operation. Mark which examples you can complete from saved synthetic JSON alone.
Expected observation: most conceptual exercises need no live credentials. Before any optional read, verify the context through your normal trusted setup and confirm permission. Record commands as proposed until executed. Never copy private kubeconfig contents into a public evidence packet.
Troubleshooting and trade-offs
If a command reports a missing context, stop rather than creating or guessing one. If authentication fails, use the organization’s normal access process. Do not disable certificate verification. If a feature is absent, compare its documented version and distribution prerequisites; a current website page does not upgrade an older cluster.
Interview practice
Why use explicit context and namespace?
They make the intended target visible and reduce dependence on ambient defaults. They do not replace authorization or review of the command’s effects.
Is dry-run=client guaranteed offline?
No. Depending on command, discovery, validation and configuration, client-side processing may still contact the API. Use plain local fixture analysis when network-free work is required.
Completion check
Classify each command by target and effect, and keep cluster credentials out of evidence.
Sources and version notes
Baseline checked 6 October 2026: the official release page lists Kubernetes 1.37.1. Verify your cluster and distribution prerequisites. All manifests are offline teaching examples; no cluster mutations or cloud resources are executed by this handbook.
- Official documentation: Releases
- Official documentation: Version skew policy
- Official documentation: Tools
- Official documentation: Organize cluster access kubeconfig
Make the understanding yours.
Use the completion check above. Mark this chapter when you can explain the mechanism and its limits.
Self-assessed reading progress. This does not certify that a lab ran or a system is secure.