Helm CLI Builder
Build Helm commands interactively. Install, upgrade, rollback, template, search — all flags explained. No cluster connection needed.
Action
Common Recipes
Ready-to-use Helm commands for everyday Kubernetes tasks. Click a recipe to populate the builder, or copy the command directly.
Install with custom values
Install chart with values file and overrides
helm install my-app ./my-chart -f values.yaml -f values-prod.yaml --set image.tag=v2.1.0 -n production --create-namespace
Click to load in builder
Upgrade with --install (upsert)
Upgrade or install if release doesn't exist
helm upgrade --install my-app bitnami/nginx -n production --reuse-values --set image.tag=v2.2.0 --wait --timeout 5m0s
Click to load in builder
Rollback to previous revision
Rollback a failed upgrade to the last working version
helm rollback my-app 1 -n production --wait --timeout 5m0s
Click to load in builder
List all releases
Show all releases across all namespaces
helm list --all-namespaces --all
Click to load in builder
Template render (dry run)
Render templates locally without installing
helm template my-app ./my-chart -f values.yaml --set env=staging -n staging
Click to load in builder
Add Bitnami repository
Add the Bitnami Helm chart repository
helm repo add bitnami https://charts.bitnami.com/bitnami && helm repo update
Search for a chart
Find charts matching a keyword in configured repos
helm search repo nginx --versions
Click to load in builder
Show chart default values
View all configurable values for a chart
helm show values bitnami/nginx --version 15.0.0
Click to load in builder
Pull chart locally
Download and extract chart to local directory
helm pull bitnami/nginx --version 15.0.0 --untar -d ./charts
Click to load in builder
Get release manifest
View the Kubernetes manifests of a deployed release
helm get manifest my-app -n production
Click to load in builder
Uninstall but keep history
Remove release but preserve history for rollback
helm uninstall my-app -n production --keep-history
Click to load in builder
What is Helm?
Helm is the package manager for Kubernetes. It uses "charts" — pre-configured Kubernetes resource templates — to define, install, and upgrade applications. Helm manages releases (instances of charts) and supports versioning, rollback, and dependency management.
Key Helm Concepts
- Chart — A package of Kubernetes YAML templates + values. Can come from a repo, a local directory, or a .tgz file.
- Release — An instance of a chart deployed to a cluster. Each install creates a new release.
- Repository — A collection of charts (like Bitnami, Artifact Hub). Added with
helm repo add. - Values — Configuration that customizes a chart. Passed via
-f values.yamlor--set key=value. - Revision — Each install/upgrade creates a new revision. Rollback targets a specific revision number.
Most Used Helm Commands
| Command | Purpose | Example |
|---|---|---|
| install | Deploy a chart | helm install my-app bitnami/nginx |
| upgrade | Upgrade a release | helm upgrade my-app bitnami/nginx |
| uninstall | Remove a release | helm uninstall my-app -n prod |
| rollback | Rollback to revision | helm rollback my-app 1 |
| list | List releases | helm list -A |
| template | Render templates | helm template my-app ./chart |
| repo add | Add a chart repo | helm repo add bitnami https://... |
| show values | View chart values | helm show values bitnami/nginx |
| get manifest | Get deployed YAML | helm get manifest my-app |
| pull | Download chart | helm pull bitnami/nginx --untar |
Helm Workflow
A typical Helm workflow for deploying an application:
helm repo add— Add the chart repositoryhelm search repo— Find the chart you needhelm show values— Check available configuration optionshelm install— Deploy with your custom valueshelm upgrade— Update the release when chart or values changehelm rollback— Revert if something breaks
Values Precedence
Helm merges values in order of precedence (last wins):
- Chart defaults (
values.yamlin the chart) - User-supplied values files (
-f custom.yaml, applied left-to-right) - Inline
--setoverrides (highest priority)
Use --set-string when you need values to be treated as strings (e.g., numeric-looking IDs that shouldn't be converted to numbers).
Privacy First
All command building happens in your browser. Your release names, chart references, values, and cluster details are never sent to any server.