Skip to main content
Changes to Helm releases go through your own helm, so hooks, three-way merges and Helm’s own record of revisions work as they always do. Lumovi prepares the command, shows it to you, and shows what it would change before anything does. Open a release in Helm releases (G then H), and use Upgrade…, Roll back… or Uninstall… (the trash button) at the top of its panel.

​
Upgrade

Upgrading a Helm release with new values.Upgrading a Helm release with new values.

Upgrading a release with new values.

1

Choose the chart

The chart exactly as the cluster stores it with the release. Use it to change values without touching the chart or its version.Helm doesn’t store subcharts with a release, so a chart with subcharts can’t be reused this way. Lumovi says which subcharts it has, and you pick the chart from its repository instead.
To change the chart’s version, or the chart itself. Type any of:Leave Version empty for the latest, or type one. With a repository URL, List its versions reads the repository’s index and offers every version in a menu.Or type in Search Artifact Hub and press ↵, and pick one of the charts it finds, as when you install a chart.
A chart folder or a packaged .tgz, like the one you’re working on. It’s checked with helm lint, and can have its subcharts downloaded. See Charts on your computer.Desktop app only.
2

Edit the values

The editor starts with the values set for the release now. Everything set here applies, and the chart’s defaults fill in the rest, the way helm upgrade --values works.Start from the chart’s defaults replaces the editor’s contents with the chosen chart’s values.yaml (from helm show values), for when you want to see everything you could set. It’s there for a chart from a repository, a registry or this computer, not for the chart the release runs.
3

Review

Press Review, or ⌘S in the editor (Ctrl+S on Windows and Linux). Lumovi checks the values are valid YAML, then runs the upgrade as a server-side dry run: Helm renders the chart and the API server validates every object, but nothing changes.You see The cluster accepts it, how many lines of the manifest change, the diff, and the notes the chart would print. If the cluster refuses something, you see what it said instead.
4

Upgrade

Press Upgrade to run it for real, or Back to editing to change something. The notification and the Activity log record the command.
The dialog shows the equivalent command all along, like:

​
Roll back

Roll back… lists every earlier revision with its status, age, chart and app version, and description. Pick one, and the dialog tells you what going back means: “Running now: revision 5. Going back to 3 changes 12 lines of its values and 40 of its manifest.” It runs helm rollback <release> <revision>. Helm records a rollback as a new revision, so you can always go forward again the same way. A release with a single revision has nothing to roll back to, and doesn’t offer it.
To see exactly what differs before you roll back, use the release’s History tab: pick any two revisions and compare their values or manifests.

​
Uninstall

Uninstall… says how many objects it deletes. Objects the chart keeps on purpose stay: CRDs, and anything annotated with helm.sh/resource-policy: keep. Type the release’s name to confirm. Tick Keep its history to run helm uninstall --keep-history: the revisions stay, so the release can be rolled back into being. It then shows as Uninstalled.

​
Releases Flux manages

If Flux’s helm-controller manages a release, every dialog warns that Flux puts back changes made any other way. Change it through its HelmRelease instead, or suspend that first. See Helm releases.

​
Which helm runs

The desktop app runs the helm on your login shell’s PATH, so it’s the same one your terminal uses. To use another, set LUMOVI_HELM to its path before starting Lumovi. If Lumovi can’t run it, a release’s Upgrade…, Roll back… and Uninstall… are disabled, and say why: “Lumovi uses helm for this, and couldn’t run helm. Install Helm, or set LUMOVI_HELM to where it is.” Install chart says the same when you choose Review, with Helm’s address: “Install Helm (https://helm.sh), or set LUMOVI_HELM to where it is.” Each command is pointed at the cluster you’re looking at with --kube-context, uses your kubeconfig’s credentials, and may run for up to 10 minutes (for charts with slow hooks).
In your cluster: the image includes helm, and runs it as the person signed in, with their own permissions. Charts come from repositories, registries or URLs, never from files. See What’s different.

​
When changes are off

A cluster you made read-only can’t be changed with Helm either: a release’s buttons are disabled with “Changes are turned off for this cluster.” The app itself refuses the change, not just its buttons, so Install chart, which stays enabled, shows that the cluster is read-only when you choose Review.

Charts on your computer

Upgrade from the chart you’re working on, checked with helm lint.

Install a chart

Find one on Artifact Hub, and install it with a dry run first.