← Back to all sparks
S

Strimzi

INFRA · APIS
Velocity0.0

Kubernetes operator for running and managing Apache Kafka clusters

Strimzi hit 1.0 by deleting every CRD API except v1 — conversion is mandatory before upgrade.

kafka-operatorkubernetescrd-migrationbreaking-changeversion-tracking
Current state
The operator reached 1.0.0 by removing the v1beta2, v1beta1 and v1alpha1 CRD APIs entirely and moving fully to v1, with every release since carrying the same blocking warning: convert all custom resources and upgrade the CRDs before upgrading. The 0.45.x branch was closed out with a final patch. Since 1.0, work has been Kafka version tracking — 4.3.0 and 4.2.1 added, 4.1.x dropped — plus connector lifecycle corrections.
Where it's heading
This is a project that spent its 0.x years accumulating API versions and used the 1.0 boundary to shed all of them at once. The consequence is a hard migration gate for every existing installation, which is why the warning leads every release page rather than sitting in an upgrade appendix. Post-1.0 releases look like ordinary operator maintenance: track new Kafka versions, drop old ones, fix reconciliation ordering.
Prediction
Expect the 1.1 line to reach stable and settle into a rhythm of adding each new Apache Kafka release and dropping the oldest, with the CRD conversion warning persisting until most of the installed base has moved.

Recent moves

  1. 1mo ago

    Kafka 4.3.0 support; 4.1.x dropped; connector stop semantics fixed

    Adds Kafka 4.3.0 and 4.2.1, removes 4.1.x, and corrects connector lifecycle handling so failed KafkaConnectors can be stopped while pausing them is rejected outright, since Kafka Connect does not support it. Also reorders reconciliation so Cruise Control runs before the Entity Operator.

    View source ↗
  2. 1mo ago

    1.0.1 release preparation tag

    A release-preparation tag whose body is a sign-off line. No content beyond the version bump itself.

    View source ↗
  3. 3mo ago

    Second 1.0.0 candidate fixes connector resume

    A single-fix candidate for resuming stopped or paused Kafka Connect connectors. The connector lifecycle keeps producing corrections across the 1.0 and 1.1 lines.

    View source ↗
  4. 3mo ago

    1.0 drops every CRD API but v1

    ⚡ SPARK

    The release that defines the whole window. Every subsequent entry repeats its conversion warning, and the operator's post-1.0 work has been ordinary version tracking on top of the clean API surface this created.

    View source ↗
  5. 4mo ago

    Final 0.45.x patch: CVE fixes and Kafka 3.9.2

    Closes out the 0.45 branch with dependency and CVE fixes plus Kafka 3.9.2 support, and states plainly that no further patches will follow. Anyone still on 0.45.x now has the CRD conversion ahead of them with no maintained fallback.

    View source ↗