Skip to content

fix: add --force-conflicts to helm deploy to resolve server-side apply conflict#1667

Merged
zanejohnson-azure merged 1 commit into
ci_prodfrom
zane/fix-helm-force-conflicts
May 1, 2026
Merged

fix: add --force-conflicts to helm deploy to resolve server-side apply conflict#1667
zanejohnson-azure merged 1 commit into
ci_prodfrom
zane/fix-helm-force-conflicts

Conversation

@zanejohnson-azure
Copy link
Copy Markdown
Contributor

@zanejohnson-azure zanejohnson-azure commented May 1, 2026

problem:

helm chart deployment fails in this cluster https://github-private.visualstudio.com/microsoft/_build/results?buildId=116992&view=logs&j=e0d6c3c5-8898-56d1-7145-a67bdb7b228d&t=f00d8ec0-2a89-5ba3-6227-d5b730b66c7c

why:

Helm 4 uses server-side apply by default. Someone previously used kubectl edit to modify container images, making kubectl-edit the field manager. Helm can't overwrite fields owned by another manager without explicit permission.

fix:

Add --force-conflicts to helm upgrade arguments, allowing Helm to take ownership of conflicting fields.

test:

Ran helm upgrade --force-conflicts manually against ci-logs-prod-aks-geneva-integration-multi-tenancy — succeeded (revision 22).

…y ownership conflicts

Helm 4 uses server-side apply which fails when fields were previously
modified by kubectl-edit. Adding --force-conflicts allows Helm to take
ownership of conflicting fields.
@zanejohnson-azure zanejohnson-azure requested a review from a team as a code owner May 1, 2026 18:18
@zanejohnson-azure zanejohnson-azure enabled auto-merge (squash) May 1, 2026 18:24
@zanejohnson-azure zanejohnson-azure merged commit b96f8c0 into ci_prod May 1, 2026
19 checks passed
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.

2 participants