Containers & Orchestration
Helm packages and manages Kubernetes apps as charts.
On this page
Use this page for fast recall. Use Full documentation when you want the complete end-to-end path.
A simple 5-step flow you can follow when using Helm in real work.
1) Setup
Install/run the tool and confirm version. Create a minimal config.
2) Small change
Do one small action end-to-end to prove the workflow.
3) Validate
Check output, logs, and status. Catch mistakes early.
4) Automate
Convert it into a repeatable script or pipeline step.
5) Productionize
Add safety: secrets, rollback, observability, and docs.
These are practical sequences you can copy into your own checklist or runbook.
Goal: Upgrade without surprises by rendering, reviewing, and monitoring rollout.
- Fetch current values (`helm get values`).
- Render locally (`helm template`) to review changes.
- Run `helm upgrade --install` in a namespace.
- Watch Kubernetes rollout status and events.
- Rollback using `helm rollback` if needed.
- Charts
- Templates
- Releases
Learning path (high-level):
- Chart structure
- Values management
- Release strategies
Create chart
Command
helm create my-chartInstall release
Command
helm install my-release ./my-chartUpgrade release
Command
helm upgrade my-release ./my-chartShort descriptions and practical intent. Search, filter, copy, and reuse.
Showing 20
helm versionShow Helm version.
helm repo listShow configured Helm repositories.
helm repo add bitnami https://charts.bitnami.com/bitnamiAdd a chart repository.
helm repo updateUpdate repo index.
helm search repo nginxSearch charts in repositories.
helm show values bitnami/nginxInspect default values.
helm show chart bitnami/nginxInspect chart metadata.
helm create my-chartCreate a new chart scaffold.
helm lint ./my-chartValidate chart structure.
helm template myrel ./my-chart -f values.yamlRender Kubernetes YAML locally.
helm install my-release ./my-chart -n myns --create-namespaceInstall a release.
helm upgrade my-release ./my-chart -n mynsUpgrade a release.
helm upgrade --install my-release ./my-chart -n mynsUpsert: install or upgrade.
helm list -AList releases in all namespaces.
helm status my-release -n mynsShow release status and resources.
helm get values my-release -n mynsGet the values used for a release.
helm get manifest my-release -n mynsGet rendered manifest for a release.
helm history my-release -n mynsShow revision history.
helm rollback my-release 2 -n mynsRollback to a revision.
helm uninstall my-release -n mynsRemove a release.
Small blocks you can drop into your terminal, config, or runbook.
Render YAML to review before deploy
bash
helm template myrel ./chart -n myns -f values.yaml | lessWhen things break, follow this order to stay calm and move fast.
- If install fails: check namespace, permissions, and rendered YAML (`helm template`).
- If resources look wrong: inspect the manifest (`helm get manifest`) and values used.
- If rollback is needed: use `helm history` then rollback to a known-good revision.
The common mistakes that slow people down when using Helm.
- Copy-pasting commands without understanding inputs/outputs and side effects.
- Not documenting defaults (ports, paths, credentials) and then getting stuck in prod.
- Skipping logs and metrics when troubleshooting; always collect evidence first.
Do these tasks in order. You will feel the tool instead of just reading about it.
- Install or run the tool locally (or in Docker) and verify it works with a hello-world action.
- Create a minimal config and run the most common command 3 times (with a small change each time).
- Break something on purpose and document how you debugged it in your Notes.
Use these to test if you truly understand the basics (and can explain them clearly).
- Explain the tool’s role in a real CI/CD pipeline from commit to production.
- Describe the most common failure you’ve seen with this tool and how you fixed it.
- What would you monitor/alert on for this tool in production?