⚠️ ⚠️ ⚠️ Important: From Strimzi 1.0.0, the only supported version of CRD API is v1. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported. Before upgrading to Strimzi 1.0.0 and above, make sure to convert all custom resources and upgrade the CRDs.

Main changes since 1.0

This release contains the following new features and improvements:

• Allow failed KafkaConnectors to be stopped and reject pausing of failed connectors since this operation is not supported by Kafka Connect
• Add support for Apache Kafka 4.3.0 and 4.2.1
• Remove support for Kafka 4.1.x
• Reconcile Cruise Control before Entity Operator when both are enabled.
• New Cluster operator configuration option STRIMZI_PKCS12_KEYSTORE_GENERATION to disable generating PKCS12 stores in CA and Kafka user Secret resources.
• Support for Gateway API-based type: tlsroute listener
• Support for dependency scope configuration of Maven artifacts in Kafka Connect Build
• Support for configuring per-broker listener annotation and label templates.
• Improved support for custom Apache Kafka versions
• Add UseBackgroundPodDeletion feature gate (alpha, disabled by default) to use background deletion propagation when deleting pods during rolling updates.
• Strimzi Drain Cleaner updated to 1.6.0 (included in the Strimzi installation files)
• Strimzi Access Operator updated to 0.3.0 - included in Strimzi installation files, examples, and documentation
• KafkaBridge and KafkaMirrorMaker2 now use PEM files instead of P12/JKS for TLS authentication and TLS truststore. PEM files are accessed directly from secrets using KubernetesSecretConfigProvider.
• It's now possible to configure mTLS validityDays and renewalDays for each KafkaUser

All changes can be found under the 1.1.0 milestone or in the CHANGELOG.md.

Upgrading from Strimzi 0.51.0

See the documentation for upgrade instructions.

Container images

The following container images are part of this release:

New Contributors

• @neeraj-laad made their first contribution in #12652
• @TheoBrigitte made their first contribution in #12691
• @pkotak made their first contribution in #12743
• @gilvansfilho made their first contribution in #12746
• @gaganhr94 made their first contribution in #12656
• @officialasishkumar made their first contribution in #12732
• @afausti made their first contribution in #12783
• @aveek22 made their first contribution in #12791
• @won-seoop made their first contribution in #12776
• @mahitha-ada made their first contribution in #12824
• @chon3806 made their first contribution in #12675

⚠️ ⚠️ ⚠️ Important: From Strimzi 1.0.0, the only supported version of CRD API is v1. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported. Before upgrading to Strimzi 1.0.0 and above, make sure to convert all custom resources and upgrade the CRDs.

Main changes since 1.0

This release contains the following new features and improvements:

• Allow failed KafkaConnectors to be stopped and reject pausing of failed connectors since this operation is not supported by Kafka Connect
• Add support for Apache Kafka 4.3.0 and 4.2.1
• Remove support for Kafka 4.1.x
• Reconcile Cruise Control before Entity Operator when both are enabled.
• New Cluster operator configuration option STRIMZI_PKCS12_KEYSTORE_GENERATION to disable generating PKCS12 stores in CA and Kafka user Secret resources.
• Support for Gateway API-based type: tlsroute listener
• Support for dependency scope configuration of Maven artifacts in Kafka Connect Build
• Support for configuring per-broker listener annotation and label templates.
• Improved support for custom Apache Kafka versions
• Add UseBackgroundPodDeletion feature gate (alpha, disabled by default) to use background deletion propagation when deleting pods during rolling updates.
• Strimzi Drain Cleaner updated to 1.6.0 (included in the Strimzi installation files)
• Strimzi Access Operator updated to 0.3.0 - included in Strimzi installation files, examples, and documentation
• KafkaBridge and KafkaMirrorMaker2 now use PEM files instead of P12/JKS for TLS authentication and TLS truststore. PEM files are accessed directly from secrets using KubernetesSecretConfigProvider.
• It's now possible to configure mTLS validityDays and renewalDays for each KafkaUser

All changes can be found under the 1.1.0 milestone or in the CHANGELOG.md.

Upgrading from Strimzi 0.51.0

See the documentation for upgrade instructions.

Container images

The following container images are part of this release:

New Contributors

• @neeraj-laad made their first contribution in #12652
• @TheoBrigitte made their first contribution in #12691
• @pkotak made their first contribution in #12743
• @gilvansfilho made their first contribution in #12746
• @gaganhr94 made their first contribution in #12656
• @officialasishkumar made their first contribution in #12732
• @afausti made their first contribution in #12783
• @aveek22 made their first contribution in #12791
• @won-seoop made their first contribution in #12776
• @mahitha-ada made their first contribution in #12824
• @chon3806 made their first contribution in #12675

⚠️ ⚠️ ⚠️ Important: Strimzi 1.0.1 supports only the new v1 CRD API. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported. Before upgrading to Strimzi 1.0.1, make sure to convert all custom resources and upgrade the CRDs.

Main changes since 1.0.0

• Entity Operator cross-namespace watching is now controlled by the STRIMZI_ENTITY_OPERATOR_WATCHED_NAMESPACE_ENABLED environment variable in the Cluster Operator.
  This feature is now disabled by default.
  If you have watchedNamespace configured in your Kafka CR's Entity Operator sections and it differs from the cluster namespace, you must set STRIMZI_ENTITY_OPERATOR_WATCHED_NAMESPACE_ENABLED=true in the Cluster Operator deployment:

  env:
    - name: STRIMZI_ENTITY_OPERATOR_WATCHED_NAMESPACE_ENABLED
      value: "true"

• Fixes CVE-2026-55225
• Fixes CVE-2026-55226

Upgrading from Strimzi 0.51.0

See the documentation for upgrade instructions. Make sure to follow the CRD upgrade instructions!

Container images

The following container images are part of this release:

⚠️ ⚠️ ⚠️ Important: Strimzi 1.0.0 supports only the new v1 CRD API. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported. Before upgrading to Strimzi 1.0.0, make sure to convert all custom resources and upgrade the CRDs.

Main changes since 0.51

This release contains the following new features and improvements:

• Remove support for the v1beta2 API (and v1alpha1 and v1beta2 for KafkaTopic and KafkaUser) and fully move to the v1 API
• Add support for Kafka 4.1.2
• Add support for advertisedPortTemplate in listener configuration to add more flexibility when configuring advertised ports.
• Support for type: environment-variable rack awareness based on environment variables that do not require ClusterRoleBindings
• Add support for TLS/SSL on the HTTP Bridge
• Add support for force-renewal of KafkaUser certificates via strimzi.io/force-renew annotation
• The UseConnectBuildWithBuildah feature gate moves to the beta stage and is enabled by default
• And many more ...

All changes can be found under the 1.0.0 milestone or in the CHANGELOG.md.

Upgrading from Strimzi 0.51.0

See the documentation for upgrade instructions. Make sure to follow the CRD upgrade instructions!

Container images

The following container images are part of this release:

New Contributors

• @marvin-roesch made their first contribution in #12477
• @Paramesh324 made their first contribution in #12509
• @marcelojscosta made their first contribution in #12527
• @QuentinBisson made their first contribution in #12560
• @guancioul made their first contribution in #12631
• @mamccorm made their first contribution in #12506

⚠️ ⚠️ ⚠️ Important: Strimzi 1.0.0 supports only the new v1 CRD API. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported. Before upgrading to Strimzi 1.0.0, make sure to convert all custom resources and upgrade the CRDs.

Main changes since 1.0.0-rc1

• Fix resuming stopped or paused Kafka Connect connectors

All changes can be found under the 1.0.0 milestone or in the CHANGELOG.md.

Upgrading from Strimzi 0.51.0 or 1.0.0-rc1

See the documentation for upgrade instructions.

Container images

The following container images are part of this release:

⚠️ ⚠️ ⚠️ Important: Strimzi 1.0.0 supports only the new v1 CRD API. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported. Before upgrading to Strimzi 1.0.0, make sure to convert all custom resources and upgrade the CRDs.

Main changes since 0.51

This release contains the following new features and improvements:

• Remove support for the v1beta2 API (and v1alpha1 and v1beta2 for KafkaTopic and KafkaUser) and fully move to the v1 API
• Add support for Kafka 4.1.2
• Add support for advertisedPortTemplate in listener configuration to add more flexibility when configuring advertised ports.
• Support for type: environment-variable rack awareness based on environment variables that do not require ClusterRoleBindings
• Add support for TLS/SSL on the HTTP Bridge
• Add support for force-renewal of KafkaUser certificates via strimzi.io/force-renew annotation
• The UseConnectBuildWithBuildah feature gate moves to the beta stage and is enabled by default
• And many more ...

All changes can be found under the 1.0.0 milestone or in the CHANGELOG.md.

Upgrading from Strimzi 0.51.0

See the documentation for upgrade instructions.

Container images

The following container images are part of this release:

New Contributors

• @marvin-roesch made their first contribution in #12477
• @Paramesh324 made their first contribution in #12509
• @marcelojscosta made their first contribution in #12527
• @QuentinBisson made their first contribution in #12560
• @guancioul made their first contribution in #12631
• @mamccorm made their first contribution in #12506

⚠️ Important: Strimzi 0.45 supports only Kubernetes 1.25 and newer. Kubernetes 1.23 and 1.24 are not supported anymore.

⚠️ Important: Strimzi 0.45.2 is the last patch release from the 0.45.x release branch, there will be no other patch release after this one.

⚠️ Important: For upgrades to Strimzi 0.46 and above, pay attention to the Upgrade to Strimzi 0.46-0.51 section of this release page.

Main changes since 0.45.1

This release contains the following new features and improvements:

• Dependency updates and CVE fixes
• Add support for Kafka 3.9.2

All changes can be found under the 0.45.2 milestone.

Watch out also for some notable changes, deprecations, and removals:

• Strimzi 0.45 is the last minor Strimzi version with support for ZooKeeper-based Apache Kafka clusters and MirrorMaker 1 deployments.
  Please make sure to migrate to KRaft and MirrorMaker 2 before upgrading to Strimzi 0.46 or newer.
• Strimzi 0.45 is the last Strimzi version to include the Strimzi EnvVar Configuration Provider (deprecated in Strimzi 0.38.0) and Strimzi MirrorMaker 2 Extensions (deprecated in Strimzi 0.28.0).
  Please use the Apache Kafka EnvVarConfigProvider and Identity Replication Policy instead.

Upgrade to Strimzi 0.46-0.51

Upgrade to Strimzi 0.46-0.51 is possible, however, if you are currently using Kafka 3.9.2, the operator will fail after the upgrade with an error similar to this:

2026-03-07 17:16:15 WARN  AbstractOperator:567 - Reconciliation #15(watch) Kafka(myproject/my-cluster): Failed to reconcile
io.strimzi.operator.cluster.model.KafkaUpgradeException: Unsupported Kafka.spec.kafka.version: 3.9.2. Supported versions are: [4.1.1, 4.2.0, 4.0.0, 4.0.1, 4.1.0, 3.0.0, 3.2.3, 3.3.2, 3.4.1, 3.5.0, 3.5.1, 3.6.0, 3.5.2, 3.6.1, 3.7.0, 3.6.2, 3.7.1, 3.8.0, 3.0.1, 3.1.0, 3.1.1, 3.2.0, 3.1.2, 3.2.1, 3.3.1, 3.4.0, 2.1.0, 3.8.1, 3.9.0, 3.9.1, 2.6.2, 2.7.1, 2.8.0, 2.8.1, 2.5.1, 2.6.0, 2.6.1, 2.7.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.1.1, 2.2.0, 2.2.1, 2.3.0]
        at io.strimzi.operator.cluster.model.KafkaVersion$Lookup.version(KafkaVersion.java:148)
        at io.strimzi.operator.cluster.operator.assembly.KRaftVersionChangeCreator.detectToAndFromVersions(KRaftVersionChangeCreator.java:157)
        at io.vertx.core.impl.future.Composition.complete(Composition.java:40)
        at io.vertx.core.impl.future.FutureBase.lambda$emitResult$0(FutureBase.java:59)
        at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:148)
        at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:141)
        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:535)
        at io.netty.channel.SingleThreadIoEventLoop.run(SingleThreadIoEventLoop.java:201)
        at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:1195)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:1583)

When that happens, use the following command to update the Kafka version annotation on the Kafka Pods:

kubectl annotate pod -l strimzi.io/kind=Kafka,strimzi.io/component-type=kafka,strimzi.io/cluster=CLUSTER_NAME strimzi.io/kafka-version=3.9.1 --overwrite -n NAMESPACE_NAME

Where CLUSTER_NAME is the name of your cluster and NAMESPACE_NAME is its namespace.

Once you change the annotation, the upgrade will proceed.

Upgrading from Strimzi 0.45.1

See the documentation for upgrade instructions.

Upgrading from Strimzi 0.22 or earlier

Direct upgrade from Strimzi 0.22 or earlier is not supported anymore! You have to upgrade first to one of the previous versions of Strimzi. You will also need to convert the CRD resources. For more details, see the documentation.

Container images

The following container images are part of this release:

New Contributors

• @shub-est made their first contribution in #12237

What's Changed

• [release-0.45.x][ST] Fix setup Minio and freeze Minio version by @im-konge in #11587
• [AZP] Add cleanup phase to UTs/ITs job for build - release-0.45.x branch by @im-konge in #11896
• Fix kuberntes-client exclusion by @fvaleri in #11892
• [release-0.45.x] Fix Postgres issue in STs and clean the cache by @im-konge in #12045
• Bumped Vert.x and Netty to fix CVEs on 0.45.x branch by @ppatierno in #12060
• Bumped Vertx 4.5.22 and Netty 4.1.128.Final on 0.45.x branch by @ppatierno in #12064
• Upgrade Zookeeper to remediate CVE-2024-47554 by @shub-est in #12237
• Upgraded Nimbus Jose JWT to 10.0.2 to remediate CVE-2025-53864 by @shub-est in #12247
• Upgraded GRPC Netty Shaded to remediate CVE-2025-55163 by @shub-est in #12251
• Upgraded Cruise Control to 2.5.146 by @shub-est in #12255
• Updated Netty to 4.1.130.Final to resolve CVE-2025-67735 by @shub-est in #12286
• Updated Apache Log4J to 2.25.3 to remediate CVE-2025-68161 by @shub-est in #12288
• Update Vertx to 4.5.24 to remediate CVE-2026-1002 by @shub-est in #12367
• Add support for Kafka 3.9.2 by @im-konge in #12321
• Update Kafka Exporter to 1.9.0 - release-0.45.x by @im-konge in #12449
• [release-0.45.x] Update CHANGELOG with information about CVE fixes and other information by @im-konge in #12460
• Update Jackson to address CVE GHSA-72hv-8253-57qq by @MichaelMorrisEst in #12485

⚠️ Important: Strimzi 0.45 supports only Kubernetes 1.25 and newer. Kubernetes 1.23 and 1.24 are not supported anymore.

⚠️ Important: Strimzi 0.45.2 is the last patch release from the 0.45.x release branch, there will be no other patch release after this one.

⚠️ Important: For upgrades to Strimzi 0.46 and above, pay attention to the Upgrade to Strimzi 0.46-0.51 section of this release page.

Main changes since 0.45.1

This release contains the following new features and improvements:

• Dependency updates and CVE fixes
• Add support for Kafka 3.9.2

All changes can be found under the 0.45.2 milestone.

Watch out also for some notable changes, deprecations, and removals:

• Strimzi 0.45 is the last minor Strimzi version with support for ZooKeeper-based Apache Kafka clusters and MirrorMaker 1 deployments.
  Please make sure to migrate to KRaft and MirrorMaker 2 before upgrading to Strimzi 0.46 or newer.
• Strimzi 0.45 is the last Strimzi version to include the Strimzi EnvVar Configuration Provider (deprecated in Strimzi 0.38.0) and Strimzi MirrorMaker 2 Extensions (deprecated in Strimzi 0.28.0).
  Please use the Apache Kafka EnvVarConfigProvider and Identity Replication Policy instead.

Maven artifacts

To test the Maven artifacts that are part of this release, use the 0.45.2-RC1 version in your pom.xml.

Upgrade to Strimzi 0.46-0.51

Upgrade to Strimzi 0.46-0.51 is possible, however, if you are currently using Kafka 3.9.2, the operator will fail after the upgrade with an error similar to this:

2026-03-07 17:16:15 WARN  AbstractOperator:567 - Reconciliation #15(watch) Kafka(myproject/my-cluster): Failed to reconcile
io.strimzi.operator.cluster.model.KafkaUpgradeException: Unsupported Kafka.spec.kafka.version: 3.9.2. Supported versions are: [4.1.1, 4.2.0, 4.0.0, 4.0.1, 4.1.0, 3.0.0, 3.2.3, 3.3.2, 3.4.1, 3.5.0, 3.5.1, 3.6.0, 3.5.2, 3.6.1, 3.7.0, 3.6.2, 3.7.1, 3.8.0, 3.0.1, 3.1.0, 3.1.1, 3.2.0, 3.1.2, 3.2.1, 3.3.1, 3.4.0, 2.1.0, 3.8.1, 3.9.0, 3.9.1, 2.6.2, 2.7.1, 2.8.0, 2.8.1, 2.5.1, 2.6.0, 2.6.1, 2.7.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.1.1, 2.2.0, 2.2.1, 2.3.0]
        at io.strimzi.operator.cluster.model.KafkaVersion$Lookup.version(KafkaVersion.java:148)
        at io.strimzi.operator.cluster.operator.assembly.KRaftVersionChangeCreator.detectToAndFromVersions(KRaftVersionChangeCreator.java:157)
        at io.vertx.core.impl.future.Composition.complete(Composition.java:40)
        at io.vertx.core.impl.future.FutureBase.lambda$emitResult$0(FutureBase.java:59)
        at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:148)
        at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:141)
        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:535)
        at io.netty.channel.SingleThreadIoEventLoop.run(SingleThreadIoEventLoop.java:201)
        at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:1195)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:1583)

When that happens, use the following command to update the Kafka version annotation on the Kafka Pods:

kubectl annotate pod -l strimzi.io/kind=Kafka,strimzi.io/component-type=kafka,strimzi.io/cluster=CLUSTER_NAME strimzi.io/kafka-version=3.9.1 --overwrite -n NAMESPACE_NAME

Where CLUSTER_NAME is the name of your cluster and NAMESPACE_NAME is its namespace.

Once you change the annotation, the upgrade will proceed.

Upgrading from Strimzi 0.45.1

See the documentation for upgrade instructions.

Upgrading from Strimzi 0.22 or earlier

Direct upgrade from Strimzi 0.22 or earlier is not supported anymore! You have to upgrade first to one of the previous versions of Strimzi. You will also need to convert the CRD resources. For more details, see the documentation.

Container images

The following container images are part of this release:

New Contributors

• @shub-est made their first contribution in #12237

What's Changed

• [release-0.45.x][ST] Fix setup Minio and freeze Minio version by @im-konge in #11587
• [AZP] Add cleanup phase to UTs/ITs job for build - release-0.45.x branch by @im-konge in #11896
• Fix kuberntes-client exclusion by @fvaleri in #11892
• [release-0.45.x] Fix Postgres issue in STs and clean the cache by @im-konge in #12045
• Bumped Vert.x and Netty to fix CVEs on 0.45.x branch by @ppatierno in #12060
• Bumped Vertx 4.5.22 and Netty 4.1.128.Final on 0.45.x branch by @ppatierno in #12064
• Upgrade Zookeeper to remediate CVE-2024-47554 by @shub-est in #12237
• Upgraded Nimbus Jose JWT to 10.0.2 to remediate CVE-2025-53864 by @shub-est in #12247
• Upgraded GRPC Netty Shaded to remediate CVE-2025-55163 by @shub-est in #12251
• Upgraded Cruise Control to 2.5.146 by @shub-est in #12255
• Updated Netty to 4.1.130.Final to resolve CVE-2025-67735 by @shub-est in #12286
• Updated Apache Log4J to 2.25.3 to remediate CVE-2025-68161 by @shub-est in #12288
• Update Vertx to 4.5.24 to remediate CVE-2026-1002 by @shub-est in #12367
• Add support for Kafka 3.9.2 by @im-konge in #12321
• Update Kafka Exporter to 1.9.0 - release-0.45.x by @im-konge in #12449
• [release-0.45.x] Update CHANGELOG with information about CVE fixes and other information by @im-konge in #12460
• Update Jackson to address CVE GHSA-72hv-8253-57qq by @MichaelMorrisEst in #12485

⚠️ ⚠️ ⚠️ SECURITY: Strimzi 0.50.1 and 0.51.0 addresses CVE-2026-27133 and CVE-2026-27134. If you use Strimzi 0.47.0 or newer, please read the advisories and if you are affected, please upgrade to 0.50.1 or 0.51.0.

⚠️ Important: Strimzi 0.51 supports only Kubernetes 1.30 and newer. Kubernetes 1.27, 1.28, and 1.29 are not supported anymore.

⚠️ Important: Strimzi 0.49 introduced new API version v1 to all Strimzi custom resources.

• Make sure to Upgrade the CRDs as part of the Strimzi upgrade as well (especially when using Helm).
• The old API versions (v1alpha1, v1beta1, and v1beta2) will continue to be supported until Strimzi 1.0.0 / 0.52.0.
• Before upgrading to Strimzi 0.51.0 from Strimzi 0.48 or older, make sure that you update your KafkaUser resources to use the .spec.authorization.acls[]operations field instead of the deprecated .spec.authorization.acls[]operation.
• For more details about the migration to the v1 API and CRD upgrades, see the documentation.

Main changes since 0.50

This release contains the following new features and improvements:

• Add support for Kafka 4.2.0 and remove support for Kafka 4.0.0 and 4.0.1
• Allow configuration of additional Kafka options on a per-listener basis (connections.max.reauth.ms, max.connections, max.connections.* and max.connection.creation.rate)
• ServerSideApplyPhase1 feature gate moved to beta, and is now enabled by default

All changes can be found under the 0.51.0 milestone.

Major changes, deprecations, and removals

There are also many important changes, deprecations, and removals:

• The ingress listener type is deprecated due to the archiving of the Ingress NGINX Controller for Kubernetes (March 2026).
  The code remains in the Strimzi codebase, but no further improvements or development are planned.

Upgrading from Strimzi 0.50.0

See the documentation for upgrade instructions.

Container images

The following container images are part of this release:

New Contributors

• @alephys26 made their first contribution in #12368
• @Pinimo made their first contribution in #12366
• @mastermaxx03 made their first contribution in #12385
• @nbarrientos made their first contribution in #12401

⚠️ ⚠️ ⚠️ SECURITY: Strimzi 0.50.1 and 0.51.0 addresses CVE-2026-27133 and CVE-2026-27134. If you use Strimzi 0.47.0 or newer, please read the advisories and if you are affected, please upgrade to 0.50.1 or 0.51.0.

⚠️ Important: Strimzi 0.51 supports only Kubernetes 1.30 and newer. Kubernetes 1.27, 1.28, and 1.29 are not supported anymore.

⚠️ Important: Strimzi 0.49 introduced new API version v1 to all Strimzi custom resources.

• Make sure to Upgrade the CRDs) as part of the Strimzi upgrade as well (especially when using Helm).
• The old API versions (v1alpha1, v1beta1, and v1beta2) will continue to be supported until Strimzi 1.0.0 / 0.52.0.
• Before upgrading to Strimzi 0.51.0 from Strimzi 0.48 or older, make sure that you update your KafkaUser resources to use the .spec.authorization.acls[]operations field instead of the deprecated .spec.authorization.acls[]operation.
• For more details about the migration to the v1 API and CRD upgrades, see the documentation.

Main changes since 0.51.0-rc1

• Fix Server Side Apply handling when updating Config Maps with Connector offsets and Rebalance progress
• Documentation improvements

Maven artifacts

To test the Maven artifacts that are part of this release, use the 0.51.0-RC2 version in your pom.xml.

Upgrading from Strimzi 0.50.0

See the documentation for upgrade instructions.

Container images

The following container images are part of this release: