Main changes since 0.30
This is the last version of Strimzi with support for Kubernetes 1.16, 1.17 and 1.18!
- Support for Kafka 3.2.1
- Updated Kaniko builder to 1.9.0 and Maven builder to 1.14
- Updated Kafka Exporter to 1.6.0
- Pluggable Pod Security Profiles with built-in support for restricted Kubernetes Security Profile
- Support for leader election and running multiple operator replicas (1 active leader replicas and one or more stand-by replicas)
- Updated Strimzi Kafka Bridge to 0.22.0
- Support for IPv6 addresses being used in Strimzi issued certificates
- Make it easier to wait for custom resource readiness when using the Strimzi api module
- StrimziPodSet reconciliation metrics
All changes can be found under the 0.31.0 milestone.
Deprecations and removals
- Strimzi 0.31.0 (and any possible patch releases) is the last Strimzi version with support for Kubernetes 1.16, 1.17 and 1.18.
From Strimzi 0.32.0 on, we will support only Kubernetes 1.19 and newer.
The supported Kubernetes versions will be re-evaluated again in Q1/2023. - The
type: jaegertracing support based on Jaeger clients and OpenTracing API is now deprecated.
Because the Jaeger clients are retired and the OpenTracing project is archived, we cannot guarantee their support for future Kafka versions.
In the future, we plan to replace it with a new tracing feature based on the OpenTelemetry project.
Upgrading from Strimzi 0.30
See the documentation for upgrade instructions.
Upgrading from Strimzi 0.22 or earlier
This release supports only the API version v1beta2 and CRD version apiextensions.k8s.io/v1. If upgrading from Strimzi 0.22, migration to v1beta2 needs to be completed for all Strimzi CRDs and CRs before the upgrade to 0.31 is done! If upgrading from Strimzi version earlier than 0.22, you need to first install the CRDs from Strimzi 0.22 and complete the migration to v1beta2 for all Strimzi CRDs and CRs before the upgrade to 0.31 is done!
For more details about the CRD upgrades, see the documentation.