⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!

Main changes since 0.37

This release contains the following new features and improvements:

• Add support for Apache Kafka 3.6.0 and drop support for 3.4.0 and 3.4.1
• Sign containers using cosign
• Generate and publish Software Bill of Materials (SBOMs) of Strimzi containers
• Add support for stopping connectors according to Strimzi Proposal #54
• Allow manual rolling of Kafka Connect and Kafka Mirror Maker 2 pods using the strimzi.io/manual-rolling-update annotation (supported only when StableConnectIdentities feature gate is enabled)
• Make sure brokers are empty before scaling them down
• Add support for pausing reconciliations to the Unidirectional Topic Operator
• Allow running ZooKeeper and KRaft-based Apache Kafka clusters in parallel when the +UseKRaft feature gate is enabled
• Add support for metrics to the Unidirectional Topic Operator
• Added the includeAcceptHeader option to OAuth client and listener authentication configuration and to keycloak authorization. If set to false it turns off sending of Accept header when communicating with OAuth / OIDC authorization server. This feature is enabled by the updated Strimzi Kafka OAuth library (0.14.0).
• Update HTTP bridge to latest 0.27.0 release

It also has several notable changes, deprecations, and removals:

• The Kafka.KafkaStatus.ListenerStatus.type property has been deprecated for a long time, and now we do not use it anymore. The current plan is to completely remove this property in the next schema version. If needed, you can use the Kafka.KafkaStatus.ListenerStatus.name property, which has the same value.
• Added strimzi.io/kraft annotation to be applied on Kafka custom resource, together with the +UseKRaft feature gate enabled, to declare a ZooKeeper or KRaft based cluster.
  • if enabled the Kafka resource defines a KRaft-based cluster.
  • if disabled, missing or any other value, the operator handle the Kafka resource as a ZooKeeper-based cluster.
• The io.strimzi.kafka.EnvVarConfigProvider configuration provider is now deprecated and will be removed in Strimzi 0.42. Users should migrate to Kafka's implementation, org.apache.kafka.common.config.provider.EnvVarConfigProvider, which is a drop-in replacement. For example:

  config:
    # ...
    config.providers: env
    config.providers.env.class: io.strimzi.kafka.EnvVarConfigProvider
    # ...
  

  becomes

  config:
    # ...
    config.providers: env
    config.providers.env.class: org.apache.kafka.common.config.provider.EnvVarConfigProvider
    # ...
  
  

All changes can be found under the 0.38.0 milestone.

Maven artifacts

To test the Maven artifacts that are part of this release, use the staging repository by including the following in your pom.xml:

  <repositories>
    <repository>
      <id>staging</id>
      <url>https://oss.sonatype.org/content/repositories/iostrimzi-1205/</url>
    </repository>
  </repositories>

Upgrading from Strimzi 0.37.0

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: