artifacthub helm/strimzi/strimzi-kafka-operator 0.32.0

latest releases: 0.43.0, 0.42.0, 0.41.0...
23 months ago

Main changes since 0.31

⚠️ Important: From Strimzi 0.32.0, Strimzi supports only Kubernetes 1.19 and newer! Kubernetes versions 1.16, 1.17 and 1.18 are not supported anymore.

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

  • Add support for Kafka 3.3.1 and remove support for Kafka 3.1.0, 3.1.1, and 3.1.2
  • Update KafkaConnector CR status so the 'NotReady' condition is added if the connector or any tasks are reporting a 'FAILED' state.
  • Add auto-approval mechanism on KafkaRebalance resource when an optimization proposal is ready
  • The ControlPlaneListener feature gate moves to GA
  • Add client rack-awareness support to Strimzi Bridge pods
  • Add support for OpenTelemetry for distributed tracing
  • ZookeeperRoller considers unready pods
  • Support multiple operations per ACLRule
  • Add new listener type "cluster-ip" which is using per-broker services instead of the pod DNS names
  • Update Strimzi OAuth library to 0.11.0

All changes can be found under the 0.32.0 milestone.

⚠️ Important: Strimzi OpenTelemetry support moving from Jaeger to OLTP exporter

This release has OpenTelemetry support by using the Jaeger exporter by default.
This exporter needs a Jaeger endpoint to send traces to.
OpenTelemetry project encourages use of the OLTP exporter and will deprecate and remove the Jaeger exporter in the future.
For this reason, the Strimzi project is going to move from the Jaeger exporter to the OTLP exporter for the next releases.
In order to use it, the minimum version of the Jaeger backend has to be 1.35 because it's the first version exposing an OLTP endpoint for getting traces from such an OLTP exporter.
When the migration is done, Strimzi users can still use the Jaeger exporter if they want by building their own image with the opentelemetry-exporter-jaeger library and setting OTEL_TRACES_EXPORTER=jaeger environment variable.

Upgrading from Strimzi 0.31.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.

Don't miss a new strimzi-kafka-operator release

NewReleases is sending notifications on new releases.