Drive Your First Cluster with kubectl Verbs
Practice kubectl get, describe, and explain on a pre-built kind cluster before touching any YAML.
Lab overview
Kubernetes is an API-driven control plane: every Pod, Service, Deployment, and Node in your cluster is a typed object stored in the API server's etcd database. The kubectl command-line tool is the canonical client to that API, and every troubleshooting session, exam task, and incident response begins the same way - by reading object state with kubectl. Operators who can fluently navigate kubectl get, describe, and explain resolve issues faster than those who jump straight to writing manifests, because they can see what the cluster actually thinks is happening before changing anything.
In this lab, you will drive a pre-provisioned kind Kubernetes cluster using only read-only kubectl verbs. You will list workloads across namespaces, switch between human-readable and YAML output to see the fields the API server actually stores, describe a Node to read its capacity and events, and use kubectl explain as an offline manual page for every resource kind in the cluster. No Pods will be created in this lab - the goal is to build muscle memory for the reading half of the kubectl workflow before you start applying YAML in later labs.
Objectives
Upon completion of this beginner level lab, you will be able to:
- List Pods, Nodes, Services, and Deployments in the default namespace and across all namespaces using
kubectl get - Switch between
-o wide,-o yaml, and-o jsonpathoutput formats and read the resulting object representations - Inspect the kind control-plane Node with
kubectl describeto identify capacity, conditions, and recent events - Use
kubectl explainrecursively to navigate the Pod spec schema down to container-level fields - Discover every namespaced and cluster-scoped resource kind in the cluster with
kubectl api-resources
Who is this lab for?
This lab is designed for:
- Engineers and students taking their first hands-on steps with Kubernetes
- Learners preparing for the CKA, CKAD, or CKS certification exams
- DevOps practitioners who want to ground their kubectl workflow in reading state before writing manifests
Verified against your live environment
An automated validation engine inspects your actual resources and configurations as you work. Completion means the task was performed — not multiple choice, real-world proficiency.
More labs like this
Understand Cluster DNS and Resolve Services by Name
Walk the Kubernetes FQDN ladder, resolve Services across namespaces, and compare ClusterIP versus headless DNS records using CoreDNS.
Inspect, Create, and Debug Your First Pod with kubectl
Author a Pod, watch its lifecycle, debug an ImagePullBackOff with describe, then prove a multi-container Pod shares localhost networking and an emptyDir volume.
Terraform Providers - Configure, Version, and Lock Dependencies
Configure the AWS Terraform provider with version constraints, explore the dependency lock file, and upgrade provider versions safely.
Related reading
Environment
Every lab includes
- Real environment, pre-credentialed
- Automated checks on every step
- Isolated sandbox, auto cleanup
- AI-recommended next steps
Lab curriculum
- 01
Getting Started with Kubernetes IDE
1 automated check
- 02
List Cluster Objects Across All Namespaces
1 automated check
- 03
Switch Output Formats and Describe a Node
1 automated check
- 04
Explore Resource Schema with kubectl Explain
1 automated check
Skills validated
Not the lab you were looking for?
Browse 150+ hands-on labs across AWS, Azure, Kubernetes, Docker, and cloud security.