Skip to main content

Documentation Index

Fetch the complete documentation index at: https://radarhq.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

Radar reads the Helm release secrets directly from K8s (no helm binary needed), so every release shows up automatically. From there you can see what’s running, diff revisions, upgrade, rollback, or uninstall. Radar Helm view - releases with status, revision history, and a per-revision values diff

​
What you see

The Helm view lists every release, scoped to namespace or cluster-wide:
  • Release name, namespace, chart, chart version, app version.
  • Status (deployed, pending, failed).
  • Revision number and last deploy time.
  • Owning resources (Deployments / StatefulSets / etc. that the release manages).
Click a release for the detail view:
  • Resources - every K8s resource in this release, linked to its row in the resource browser.
  • Values - the user-supplied values, side by side with the chart defaults.
  • Manifest - the fully rendered manifest as Helm produced it.
  • Notes - the chart’s NOTES.txt.
  • History - all revisions with timestamps, descriptions, and a per-revision diff.

​
Diffs that read like git

Each revision shows a structured diff against the previous one:
  • Manifest diff - line-by-line YAML diff of the rendered manifests.
  • Values diff - which values changed.
  • Resource diff - which K8s resources were added / updated / deleted.

​
Upgrades, rollbacks, uninstalls

ActionWhat Radar runsRBAC needed
Upgrade with overridesHelm release upgrade with new valuesrbac.helm: true (broad write)
RollbackHelm release rollback to a chosen revisionrbac.helm: true
UninstallHelm release deleterbac.helm: true
InspectRead the release secretDefault RBAC
Read-only mode: pass --disable-helm-write (or run without rbac.helm) and the action buttons disappear; you still see everything.

​
Repository support

Radar shows installed releases regardless of where the chart came from - public repos, OCI registries, local archives, anything. There’s no “add repo” step in Radar; that’s a deploy-time concern. For upgrades, you can supply:
  • A new version of the same chart (Radar resolves it via the chart’s home/urls from the original install).
  • A different OCI reference.
  • A local chart archive uploaded through the dialog.

​
Concurrent edits

If two operators try to upgrade the same release at the same time, Helm’s own lock (the release pending-upgrade state) wins - Radar surfaces the conflict instead of silently overwriting. Failed upgrades show the failure reason and offer a one-click rollback.

​
See also