Skip to content

fix: enable ServerSideApply when ForceConflicts is set for Helm v4 compatibility#1661

Merged
gianlucam76 merged 1 commit intoprojectsveltos:mainfrom
gianlucam76:service-side
Mar 23, 2026
Merged

fix: enable ServerSideApply when ForceConflicts is set for Helm v4 compatibility#1661
gianlucam76 merged 1 commit intoprojectsveltos:mainfrom
gianlucam76:service-side

Conversation

@gianlucam76
Copy link
Copy Markdown
Member

Helm v4 introduced a validation that rejects ForceConflicts = true when ServerSideApply is disabled, returning:

invalid client update option(s): forceConflicts enabled when serverSideApply disabled

Both getHelmInstallClient and getHelmUpgradeClient were setting ForceConflicts = true unconditionally without enabling ServerSideApply, causing all Helm chart installs and upgrades to fail when running against Helm v4.

Fix: set ServerSideApply = true alongside ForceConflicts = true in both client builders.

…mpatibility

Helm v4 introduced a validation that rejects ForceConflicts = true when ServerSideApply
is disabled, returning:

`invalid client update option(s): forceConflicts enabled when serverSideApply disabled`

Both getHelmInstallClient and getHelmUpgradeClient were setting ForceConflicts = true unconditionally
without enabling ServerSideApply, causing all Helm chart installs and upgrades to fail when running
against Helm v4.

Fix: set ServerSideApply = true alongside ForceConflicts = true in both client builders.
@gianlucam76 gianlucam76 merged commit 58dcb28 into projectsveltos:main Mar 23, 2026
8 checks passed
@gianlucam76 gianlucam76 deleted the service-side branch March 23, 2026 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant