Skip to content

fix(deploy): the Strimzi helm install skips the CRDs kates deploy already applied - #449

Closed
bmscomp wants to merge 1 commit into
mainfrom
fix/strimzi-skip-crds
Closed

bmscomp wants to merge 1 commit into
mainfrom
fix/strimzi-skip-crds

Conversation

@bmscomp

@bmscomp bmscomp commented Oct 22, 2026

Copy link
Copy Markdown
Owner

Problem

kates deploy failed in Group A on a fresh Strimzi install with Helm 4:

failed to install CRD crds/040-Crd-kafka.yaml: conflict occurred while applying object /kafkas.kafka.strimzi.io ... Apply failed with 1 conflict: conflict with "kubectl": .spec.versions

applyLocalStrimziCRDs server-side-applies the Strimzi CRDs (kubectl apply --server-side --force-conflicts), so kubectl owns their fields. helm upgrade --install then applies the chart's crds/ again as helm, without forcing, and conflicts.

Fix

The Strimzi helm upgrade --install passes --skip-crds. The CRDs are applied once, by the step that already does it; CRD upgrades through the chart hook were already off (crdUpgrade.enabled=false).

Tests

  • TestDeployGroupA… asserts --skip-crds on the Strimzi upgrade.
  • go test ./cmd passes; golangci-lint --new-from-rev=HEAD reports 0 issues.
  • Not re-run against a live cluster.

…eady applied

applyLocalStrimziCRDs server-side-applies the Strimzi CRDs as the
"kubectl" field manager. On a fresh install Helm 4 then applies the
chart's crds/ again as "helm" without forcing, and fails with a
conflict over .spec.versions. Pass --skip-crds so the CRDs are applied
once, by the step that already owns them.
@bmscomp

bmscomp commented Oct 22, 2026

Copy link
Copy Markdown
Owner Author

Closing: #450 carries this change (fc04300) together with the stale Chart.lock fix, so one deploy gets both.

@bmscomp bmscomp closed this Oct 22, 2026
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