Skip to content

feat(kafka): gate strimzi 0.46+ upgrade on every kafka being in KRaft #4365

Open

Description

@myasnikovdaniil

#2352 migrates kafka from zookeeper to KRaft with a chart pre-upgrade hook. Record that an instance migrated is per-release state in tenant namespace, platform migrations and installer never look at it, and run-migrations.sh replays skipped slots by design while a chart hook only exists in the chart version that carries it. So release with #2352 is mandatory stop on upgrade path: cluster that jumps a minor over it lands on the strimzi bump still on zookeeper, and 0.46 dropped zookeeper to KRaft migration entirely, there is no supported path off zookeeper from there.

Right now this is a paragraph in packages/apps/kafka/README.md and nothing enforces it.

Before the bump to strimzi 0.46+ merges, we need a preflight that lists every Kafka CR in the cluster and fails the upgrade while any of them has status.kafkaMetadataState != KRaft. It should fail closed and print namespaces and releases that are still on zookeeper.

Natural place is #3458 (pre-upgrade health gate at hook weight 0, checks drop into preflight/checks/ with no runner change). If that is not merged by then, the strimzi bump PR carries its own gate.

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature
    area/platformIssues or PRs related to platform infrastructure (bundle, flux, talos, installer)
    on Sep 22, 2026
  2. added
    area/databaseIssues or PRs related to managed databases (postgres, mariadb, redis, etcd, kafka, clickhouse)
    triage/acceptedIndicates an issue is ready to be actively worked on
    priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete
    and removed
    triage/needs-triageIndicates an issue needs triage by a maintainer
    on Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/databaseIssues or PRs related to managed databases (postgres, mariadb, redis, etcd, kafka, clickhouse)area/platformIssues or PRs related to platform infrastructure (bundle, flux, talos, installer)kind/featureCategorizes issue or PR as related to a new featurepriority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to completetriage/acceptedIndicates an issue is ready to be actively worked on

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions