Helm
Buoy recognizes Helm releases through the helm virtual resource. Type helm, hr, helmrelease, or helmreleases and Buoy lists every release in scope. Releases are not real Kubernetes objects: they are synthesized from helm.sh/release.v1 Secrets, where each Secret holds a base64-gzipped JSON blob of the rendered manifest, values, notes, and hooks.
Helm Release Detail
Clicking a release opens a dedicated detail layout (the standard tabs do not apply, because there is no underlying object to fetch). The header shows the chart, app version, current revision, and overall status. Below that, a row of sections drives the body.
| Section | Contents |
|---|---|
| History (default) | Every revision of the release with status, chart version, app version, updated timestamp, and the release description. Newest first. |
| Resources | The parsed rendered manifest, grouped by kind, with each row linking to the resource’s detail view in the cluster. |
| Manifest | The rendered manifest YAML for the selected revision. |
| Values | The user-supplied values YAML for the selected revision. |
| Notes | The NOTES.txt rendered for the selected revision. |
Click a row in History to make that revision the focus of the other sections. A second selection enables a diff view: each section then shows a unified diff between the two revisions.
Actions
The Helm detail view does not run helm hooks; Buoy talks to the Kubernetes API directly. Use a helm CLI if your release relies on pre-rollback or post-uninstall hooks.
Rollback
Pick a target revision in the History tab and click Rollback. Buoy server-side-applies the target revision’s manifest, prunes resources that exist now but are missing from the target manifest, and writes a new helm.sh/release.v1 Secret with status=deployed. The previous deployed revision is demoted to superseded.
Uninstall
Deletes every resource in the deployed manifest and removes every release-history Secret. The Keep Resources option leaves the manifest’s resources in place and only drops the release-history Secrets, which is useful when you want to retain the live state but stop helm from managing it.