Core Concepts
Helm Applications
Browse every Helm release in your cluster: chart, values, rendered manifest, revision history, and dependencies, without leaving the dashboard.
On this page
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 release Secrets that Helm 3 stores in each namespace
(label owner=helm, one per revision). There’s no helm binary and no Helm SDK
embedded in the backend: it reads the same source of truth Helm itself uses.
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.
- The release list is served from a server-side cache refreshed about every 60 seconds; the page refetches every 30 seconds, so a new release shows up within about 90 seconds.
- Helm’s history stays in the cluster until a view needs it. Each revision’s Secret holds the whole release: chart, values and every rendered manifest. Since 2.6.5 the Secrets cache leaves Helm’s storage out: lists and counts read only its metadata, once a minute. A release’s payload is read when something needs it: its latest revision, once, for the Applications list or for an insight about a failed or stuck release. The Secrets list, a storage Secret’s detail and the Overview’s counts still show them.
- A release’s detail is read live, scoped to that release’s Secrets.
- Because the source is Secrets, the identity KubeBolt uses (its own ServiceAccount, or the agent’s) needs to list Secrets; without it the list answers not permitted to list Helm release secrets. Releases kept with Helm’s ConfigMap or SQL storage drivers don’t appear.
An Applications item, pinned in the cluster sidebar, shows the number of distinct releases. The Helm surface is read-only: KubeBolt does not install, upgrade, roll back or uninstall releases.
Endpoints
Both under /api/v1, for any authenticated role, on a connected cluster.
| Method | Path | Returns |
|---|---|---|
GET | /helm/releases | Cluster-wide list of releases, latest revision each |
GET | /helm/releases/{namespace}/{name} | Full detail for one release, with its revision history |
Release detail
Each release opens to a tabbed detail page. A tab with nothing to show (no dependencies, say) is hidden.
- Overview — status, revision, chart and app version, namespace, when it was updated and first deployed, the counts of resources, dependencies and revisions, and the chart’s notes.
- Values — the user-supplied values of the latest revision (what
helm get valuesreturns), read-only. The chart’s own defaults are not merged in; with none supplied the tab says the defaults are in effect. Credentials in the values, found by name and shape, are hidden. - Manifest — a master–detail explorer of every rendered object. Resources are grouped by kind in a rail you can resize (130–520px); selecting one shows its YAML, with Secret values hidden the way the YAML view hides them.
- Related — links straight to the live objects the release created (Deployments, Services, ServiceAccounts, and more).
- History — every revision with its chart and app version, status, timestamp and description, so you can see how the release evolved.
- Dependencies — the chart’s declared subcharts and their versions.
Manifest explorer
The manifest tab is built for large releases:
- Press
/to filter (case-insensitive, matching a resource’s name, kind or namespace; matches force-expand the rail). - Navigate matches with
↑/↓. - Copy the YAML of any single resource.
- Open live object jumps to that resource’s live detail view in KubeBolt, for the kinds KubeBolt has a view for (a ClusterRole, for one, is listed but not linked).
Helm insights
Two rules in the Insights Engine watch your releases and surface trouble automatically:
| Insight | Severity | Fires when |
|---|---|---|
helm-release-failed | Critical | A release’s latest revision is in the failed state: its last install or upgrade did not complete |
helm-release-hook-pending | Warning | A release has sat in a pending-* state for more than 5 minutes: typically a lifecycle hook that never completed, holding the release lock |
Both are malfunction rules: their severity is fixed and they cannot be turned off by policy, only muted per release.