Helm
Buoy lists Helm releases like any other resource. Type helm, hr, helmrelease, or helmreleases and Buoy shows every release in scope. A release isn’t a real Kubernetes object — Buoy reads it from the release history Helm keeps in the cluster.
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. Select a second revision to switch each section into a diff between the two.
Actions
Note: these actions talk to the Kubernetes API directly and do not run Helm’s chart hooks. If your release relies on
pre-rollbackorpost-uninstallhooks, use thehelmCLI instead.
Rollback
Pick a target revision in the History tab and click Rollback. Buoy reapplies that revision’s manifest, removes resources that exist now but aren’t in it, and records a new deployed revision in the release history — exactly the end state helm rollback produces.
Uninstall
Deletes every resource in the deployed manifest and clears the release history. The Keep Resources option leaves the live resources in place and only clears the history, so you keep the running state but Helm no longer manages it.