Skip to main content

rawops.dev

Skip to tool content

Helm CLI Builder

Build Helm commands interactively. Install, upgrade, rollback, template, search — all flags explained. No cluster connection needed.

command preview
Select an action below to start building your command|

Action

Common Recipes

Ready-to-use Helm commands for everyday Kubernetes tasks. Click a recipe to populate the builder, or copy the command directly.

Click to load in builder

Click to load in builder

Click to load in builder

Click to load in builder

Click to load in builder

Click to load in builder

Click to load in builder

Click to load in builder

Click to load in builder

Click to load in builder

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

Most Used Helm Commands

CommandPurposeExample
installDeploy a charthelm install my-app bitnami/nginx
upgradeUpgrade a releasehelm upgrade my-app bitnami/nginx
uninstallRemove a releasehelm uninstall my-app -n prod
rollbackRollback to revisionhelm rollback my-app 1
listList releaseshelm list -A
templateRender templateshelm template my-app ./chart
repo addAdd a chart repohelm repo add bitnami https://...
show valuesView chart valueshelm show values bitnami/nginx
get manifestGet deployed YAMLhelm get manifest my-app
pullDownload charthelm pull bitnami/nginx --untar

Helm Workflow

A typical Helm workflow for deploying an application:

  1. helm repo add — Add the chart repository
  2. helm search repo — Find the chart you need
  3. helm show values — Check available configuration options
  4. helm install — Deploy with your custom values
  5. helm upgrade — Update the release when chart or values change
  6. helm rollback — Revert if something breaks

Values Precedence

Helm merges values in order of precedence (last wins):

  1. Chart defaults (values.yaml in the chart)
  2. User-supplied values files (-f custom.yaml, applied left-to-right)
  3. Inline --set overrides (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.

Related Tools & Resources