Dry Runs with --dry-run
Asking the server to validate without applying.
Dry Runs with --dry-run is a free Helm Academy lesson on CoddyKit. This is lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Helm Academy learning path, and your progress syncs across the web and the CoddyKit app. The Helm Academy course includes 4 lessons in total.
Ask the Server First
Where helm template renders locally, --dry-run goes one step further and asks the cluster to check the manifests without applying them. 🧪
helm install my-app ./mychart --dry-runRender Plus Validate
A dry run renders your templates AND sends them to the API server for validation, then stops short of creating anything real.
It Catches Cluster Errors
Because the server sees it, --dry-run can flag issues local rendering misses, like an unknown resource kind or a schema mismatch.
Works on Upgrades Too
Add the same flag to an upgrade to preview a change against a live release before you commit to it.
helm upgrade my-app ./mychart --dry-runTwo Flavors of Dry Run
Helm offers --dry-run=client for local-only checks and --dry-run=server to also run server-side validation against your cluster.
helm upgrade my-app ./mychart --dry-run=serverClient vs Server
Client mode behaves like rendering and never needs a cluster. Server mode is stricter because the API server actually inspects the objects. 🔍
See the NOTES Too
A dry run also prints the chart's NOTES output, so you can preview the post-install hints before the release exists.
Pair It with --debug
Add --debug to a dry run for verbose output, including the computed values, making it a powerful troubleshooting combo.
helm install my-app ./mychart --dry-run --debugNo Release Is Created
Nothing is installed and no revision is recorded. A dry run leaves your cluster and your release history completely untouched.
Great for CI Gates
Because it validates against a real API server, --dry-run is a common safety check in pipelines before a deploy is allowed to proceed.
Template or Dry Run?
Use helm template when offline; reach for --dry-run when you want the cluster's opinion before installing.
Quick Check
You want the cluster to validate manifests but not create anything.
Recap
You now know --dry-run: it renders and optionally server-validates a release without creating it, in client or server mode. A safe pre-deploy check. ✅
Frequently Asked Questions
Is the “Dry Runs with --dry-run” lesson free?
Yes — the full text of “Dry Runs with --dry-run” is free to read here on the web. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Helm Academy course, upgrade to CoddyKit PRO. The Helm Academy course includes 4 lessons in total.
What will I learn in “Dry Runs with --dry-run”?
Asking the server to validate without applying. You practise Helm Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Helm Academy?
No prior experience is required. Helm Academy on CoddyKit is structured for beginners through advanced learners, so you can start here or from the beginning and move at your own pace. This is lesson 2 of 4.
How long does the “Dry Runs with --dry-run” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Helm Academy lesson?
Yes. Every Helm Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.