KubeBolt docs
ENES GitHub

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
  1. How it works
  2. Endpoints
  3. Release detail
  4. Helm insights

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.

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.

MethodPathReturns
GET/helm/releasesCluster-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.

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 latest revision is in the failed state: its last install or upgrade did not complete
helm-release-hook-pendingWarningA 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.