Skip to content

Document uninstall hook apply method follows release latching behavior #2142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
promptless-for-oss wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Document uninstall hook apply method follows release latching behavior #2142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,11 +52,12 @@ Better conflict resolution when multiple tools manage the same resources. Test i

Helm 4 will default to server-side apply when installing a new Chart release.

When upgrading (or rolling back), Helm will by default follow the previous apply method of the release.
This latching behavior is done to ensure continuity of operation for existing releases that used client-side apply.
The behavior can be overridden by setting the `--server-side` flag explicitly.
When you upgrade, roll back, or uninstall a release, Helm follows the release's previous apply method by default.
This latching behavior ensures continuity of operation for existing releases that used client-side apply.
For `helm uninstall`, the previous apply method governs the pre-delete and post-delete hooks.

@promptless-for-oss promptless-for-oss Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

helm/helm PR #32232 adds a --server-side flag (auto/true/false, default auto) to helm uninstall. Per pkg/action/uninstall.go, pre-delete and post-delete hooks previously hardcoded server-side apply to true; the change wires them through getServerSideApplyValue() so auto follows the release's stored apply method — matching upgrade and rollback. This extends the overview's latching-behavior description to cover uninstall.

Source: helm/helm#32232

To override this behavior, set the `--server-side` flag explicitly to `true` or `false`.

As such, all releases created by Helm 3 will default to using client-side apply after upgrading to Helm 4.
As such, all releases created by Helm 3 default to using client-side apply after upgrading to Helm 4.

#### Custom Template Functions
Extend Helm's templating with your own functions through plugins. Great for organization-specific templating needs.
Expand Down
Loading