Files
cozystack/packages/core
Aleksei Sviridkin 0729a6f691 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.

Without the migration hook the chart also refuses while any Strimzi CRD
still stores v1beta2: the API server would reject the v1-only CRDs of
Strimzi 1.2, and the new kafka chart rejects the Kafka 3.x versions that
the migration moves. With the hook the check would block the migration
that narrows the stored versions in the same upgrade.

While v1beta2 is served the chart also refuses while a Kafka
application sets a topic config Kafka 4 removed or a segment.bytes
below the 1 MiB minimum of Kafka 4. The new kafka chart refuses to
render such a topic, which would leave that application on its
pre-upgrade spec, and a Kafka 4 broker whose log holds the small
segment.bytes does not start. segment.bytes is read the way Kafka
reads it: trimmed, with an optional sign, leading zeros decimal.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-11-17 12:22:56 +03:00
..