World map

 

BM

World K1: The Food Court

Dry run and kubectl explain

You will learn: to rehearse a command safely, and to look up any YAML field.

Checked with Kubernetes 1.37 on 31 Oct 2026

The problem

You need a Deployment file. Twenty lines of YAML, from memory? What is the smart move?

Watch

You are here: cluster kind-dev namespace default

A dry run: A rehearsal: kubectl shows what it would do, and changes nothing. is a rehearsal. --dry-run=client -o yaml prints the order and creates nothing. get deployments proves it: no resources found.

Try it

Your turn. Add the flags that print this pod’s YAML without making it.

You are here: cluster kind-dev namespace default
dev-control-planeOpenManager

No trays here.

dev-workerOpen

No trays here.

dev-worker2Open

No trays here.

Time: +0s (sped up)

Predict

--dry-run=client stays on your laptop. --dry-run=server asks the cluster to check, then throws it away. Which one catches more mistakes?

Watch

You are here: cluster kind-dev namespace default

Forgot what a field means? kubectl explain reads the cluster’s own docs. Join the field path with dots: deployment, then spec, then replicas.

Try it

Build the command that explains a Pod’s restartPolicy.

Tap the pieces in the right order.

…

Check

Dry run or explain? Which one helps here?

Drag a card into a box. Or tap the card, then tap the box.

      You did it!

      You can now rehearse with a dry run and look up any field.

      Go deeper (optional)

      Where the story breaks: a real manager can improvise. Kubernetes can’t. It only chases what the order board says. And a closed stall’s trays never walk away. New trays are cooked elsewhere, with new names.

      Real rep (optional): try these two on your kind cluster.

      You are here: cluster kind-dev namespace default