KubeBolt / docs
GitHub

Helm Applications

Browse every Helm release in your cluster — chart, values, rendered manifest, revision history, and dependencies — without leaving the dashboard.

KubeBolt reads your Helm releases directly from the cluster and turns them into a first-class view: chart and version, the values that produced the release, the fully rendered manifest, revision history, and the chart dependency tree. It answers the question every operator eventually asks — which workload belongs to which release? — without dropping to a terminal.

How it works

KubeBolt decodes the Helm release Secrets that Helm v3 stores in each namespace. There’s no helm binary and no Helm SDK embedded in the backend — it reads the same source of truth Helm itself uses, on a 30-second sync. That keeps the image lean and means the view reflects exactly what’s installed, including releases created by CI, Argo CD, or a teammate’s laptop.

An Applications item appears in the sidebar with a counter for the number of distinct releases. As of v1.14 the Helm surface is read-only — see Roadmap for the planned write actions (upgrade, rollback, uninstall) and the chart App Center.

Endpoints

MethodPathReturns
GET/helm/releasesCluster-wide list of releases
GET/helm/releases/{namespace}/{name}Full detail for one release

Release detail

Each release opens to a tabbed detail page:

Manifest explorer

The manifest tab is built for large releases:

Helm insights

Two rules in the Insights Engine watch your releases and surface trouble automatically:

InsightSeverityFires when
helm-release-failedCriticalA release’s last install or upgrade ended in a failed state
helm-release-hook-pendingWarningA release is stuck in a pending-* state — typically a lifecycle hook that never completed, holding the release lock