Helm

Reading releases

Releases are read from Helm's own storage under either driver, with no helm binary involved: chart and app version, what your repos offer, revision, status, values, notes, the rendered manifest and the history. OCI end to end.

Installing and upgrading

Find a chart across the repositories and OCI registries you configured, then install it behind a dry run. An upgrade shows a server-rendered manifest diff before it applies.

Rollback and uninstall call the helm binary; --helm points at a different one.

Where Flux owns the release

A Flux-owned release links to its HelmRelease instead of offering an upgrade button, because Flux would revert the upgrade on its next reconcile.

The docked panel

Selecting a release docks its detail as a panel. Drag it to any side, resize it, collapse it; the placement persists, and release and releaseNs in the URL carry it through a reload or a back button.

Clicking a rendered resource opens that object in its own table with the row selected and the drawer open, while the release stays docked underneath.