You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7190f3d
Browse filesBrowse the repository at this point in the historyBrowse files
feat(platform): block the platform upgrade while a Kafka lacks KRaft
Only the isp-* variants run the platform migration hook, so on the
default variant nothing checked the Kafka clusters before the new
kafka-operator chart arrived. helm-controller replaces that chart's
CRDs before Helm runs its pre-upgrade hooks, so a guard in the operator
chart would come too late.
The platform chart now refuses to render the cozystack-packages source
while Strimzi still serves v1beta2 and any Kafka lacks KRaft evidence,
with the same evidence rule as migration 61. The check stops once only
the v1 API is served, so a NotReady tenant Kafka cannot block platform
reconciles after the upgrade.
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <[email protected]>
{{- fail (printf"KRaft is not confirmed for these Kafka clusters: %s. Strimzi 1.x cannot run ZooKeeper or an unfinished migration. Upgrade through Cozystack v1.7 and wait for each Kafka to finish its KRaft migration and report Ready. On platform variants without the migration hook, run /migrations/61 from this release's platform-migrations image before upgrading." (join ", "$unproven)) -}}
350
+
{{- end -}}
351
+
{{- elseifnot (has "v1"$served) -}}
352
+
{{- fail (printf"kafkas.kafka.strimzi.io serves neither v1beta2 nor v1 (served: %v); refusing to upgrade the platform without checking Kafka for KRaft"$served) -}}
0 commit comments