Releases: strimzi/strimzi-kafka-operator
0.31.0-rc2
Changes since 0.31.0-rc1
This is the last version of Strimzi with support for Kubernetes 1.16, 1.17 and 1.18!
- Fix Fabric8 Kubernetes client dependency version
- Improve operator memory settings
- Documentation improvements
All changes can be found under the 0.31.0 milestone.
Maven artifacts
To test the Maven artifacts which are part of this release, use the staging repository by including following in your pom.xml
:
<repositories>
<repository>
<id>staging</id>
<url>https://oss.sonatype.org/content/repositories/iostrimzi-1183</url>
</repository>
</repositories>
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.
0.31.0-rc1
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: jaeger
tracing 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.
Maven artifacts
To test the Maven artifacts which are part of this release, use the staging repository by including following in your pom.xml
:
<repositories>
<repository>
<id>staging</id>
<url>https://oss.sonatype.org/content/repositories/iostrimzi-1181</url>
</repository>
</repositories>
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.
0.30.0
Main changes since 0.29
- The
UseStrimziPodSets
feature gate moves to beta stage.
By default, StrimziPodSets are used instead of StatefulSets.
If needed,UseStrimziPodSets
can be disabled in the feature gates configuration in the Cluster Operator. - The
ServiceAccountPatching
feature gate moves to GA.
It cannot be disabled anymore and will be permanently enabled. - Remove Kafka 3.0.0 and 3.0.1
- Add support for
simple
authorization and for the User Operator to the experimentalUseKRaft
feature gate
(Note: Due to KAFKA-13909, broker restarts currently don't work when authorization is enabled.) - Add network capacity overrides for Cruise Control capacity config
- Use better encryption and digest algorithms when creating the PKCS12 stores.
For existing clusters, the certificates will not be updated during upgrade but only next time the PKCS12 store is created. - Add CPU capacity overrides for Cruise Control capacity config
- Use CustomResource existing spec and status to fix Quarkus native build's serialization
- Update JMX Exporter to version 0.17.0
- Operator emits Kubernetes Events to explain why it restarted a Kafka broker
- Better configurability of the Kafka Admin client in the User Operator
- Update Strimzi Kafka Bridge to 0.21.6
All changes can be found under the 0.30.0 milestone.
Upgrading from Strimzi 0.29
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.30 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.30 is done!
For more details about the CRD upgrades, see the documentation.
0.30.0-rc2
Changes since 0.30.0-rc1
- Mirror Maker 2 documentation improvements
- Fix unnecessary Service Account patching in every reconciliation when
imagePullSecret
are set on the Service Account - Update the Jaeger dependency in operators
pom.xml
All changes can be found under the 0.30.0 milestone.
Maven artifacts
To test the Maven artifacts which are part of this release, use the staging repository by including following in your pom.xml
:
<repositories>
<repository>
<id>staging</id>
<url>https://oss.sonatype.org/content/repositories/iostrimzi-1177</url>
</repository>
</repositories>
Upgrading from Strimzi 0.29
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.30 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.30 is done!
For more details about the CRD upgrades, see the documentation.
0.30.0-rc1
Main changes since 0.29
- The
UseStrimziPodSets
feature gate moves to beta stage.
By default, StrimziPodSets are used instead of StatefulSets.
If needed,UseStrimziPodSets
can be disabled in the feature gates configuration in the Cluster Operator. - The
ServiceAccountPatching
feature gate moves to GA.
It cannot be disabled anymore and will be permanently enabled. - Remove Kafka 3.0.0 and 3.0.1
- Add support for
simple
authorization and for the User Operator to the experimentalUseKRaft
feature gate
(Note: Due to KAFKA-13909, broker restarts currently don't work when authorization is enabled.) - Add network capacity overrides for Cruise Control capacity config
- Use better encryption and digest algorithms when creating the PKCS12 stores.
For existing clusters, the certificates will not be updated during upgrade but only next time the PKCS12 store is created. - Add CPU capacity overrides for Cruise Control capacity config
- Use CustomResource existing spec and status to fix Quarkus native build's serialization
- Update JMX Exporter to version 0.17.0
- Operator emits Kafka events to explain why it restarted a Kafka broker
- Better configurability of the Kafka Admin client in the User Operator
- Update Strimzi Kafka Bridge to 0.21.6
All changes can be found under the 0.30.0 milestone.
Maven artifacts
To test the Maven artifacts which are part of this release, use the staging repository by including following in your pom.xml
:
<repositories>
<repository>
<id>staging</id>
<url>https://oss.sonatype.org/content/repositories/iostrimzi-1176</url>
</repository>
</repositories>
Upgrading from Strimzi 0.29
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.30 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.30 is done!
For more details about the CRD upgrades, see the documentation.
0.29.0
Main changes since 0.28
- Add support for Apache Kafka 3.0.1, 3.1.1 and 3.2.0
- Increase the size of the
/tmp
volumes to 5Mi to allow unpacking of compression libraries - Use
/healthz
endpoint for Kafka Exporter health checks - Renew user certificates in User Operator only during maintenance windows
- Ensure Topic Operator using Kafka Streams state store can start up successfully
- Update Cruise Control to 2.5.89
- Remove TLS sidecar from Cruise Control pod. Cruise Control is now configured to not using ZooKeeper, so the TLS sidecar is not needed anymore.
- Allow Cruise Control topic names to be configured
- Add support for
spec.rack.topologyKey
property in Mirror Maker 2 to enable "fetch from the closest replica" feature. - Support for the s390x platform
(The s390x support is currently considered as experimental. We are not aware of any issues, but the s390x build doesn't at this point undergo the same level of testing as the AMD64 container images.) - Update Strimzi Kafka Bridge to 0.21.5
- Added rebalancing modes on the
KafkaRebalance
custom resourcefull
: this mode runs a full rebalance moving replicas across all the brokers in the cluster. This is the default one if not specified.add-brokers
: after scaling up the cluster, this mode is used to move replicas to the newly added brokers specified in the custom resource.remove-brokers
: this mode is used to move replicas off the brokers that are going to be removed, before scaling down the cluster.
- Experimental KRaft mode (ZooKeeper-less Kafka) which can be enabled using the
UseKRaft
feature gate.
Important: Use it for development and testing only!
All changes can be found under the 0.29.0 milestone.
Changes, deprecations and removals
- Since the Cruise Control TLS sidecar has been removed, the related configuration options
.spec.cruiseControl.tlsSidecar
and.spec.cruiseControl.template.tlsSidecar
in the Kafka custom resource are now deprecated.
Upgrading from Strimzi 0.28
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.29 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.29 is done!
For more details about the CRD upgrades, see the documentation.
0.29.0-rc2
Main changes since 0.29.0-rc1
- Fix Kafka, KafkaConnect and Cruise Control examples
- Fix error handling in KafkaRebalance processing
- Fix bugs in Rack-awareness and upgrade system tests
Maven artifacts
To test the Maven artifacts which are part of this release, use the staging repository by including following in your pom.xml
:
<repositories>
<repository>
<id>staging</id>
<url>https://oss.sonatype.org/content/repositories/iostrimzi-1171</url>
</repository>
</repositories>
0.29.0-rc1
Main changes since 0.28
- Add support for Apache Kafka 3.0.1, 3.1.1 and 3.2.0
- Increase the size of the
/tmp
volumes to 5Mi to allow unpacking of compression libraries - Use
/healthz
endpoint for Kafka Exporter health checks - Renew user certificates in User Operator only during maintenance windows
- Ensure Topic Operator using Kafka Streams state store can start up successfully
- Update Cruise Control to 2.5.89
- Remove TLS sidecar from Cruise Control pod. Cruise Control is now configured to not using ZooKeeper, so the TLS sidecar is not needed anymore.
- Allow Cruise Control topic names to be configured
- Add support for
spec.rack.topologyKey
property in Mirror Maker 2 to enable "fetch from the closest replica" feature. - Support for the s390x platform
(The s390x support is currently considered as experimental. We are not aware of any issues, but the s390x build doesn't at this point undergo the same level of testing as the AMD64 container images.) - Update Strimzi Kafka Bridge to 0.21.5
- Added rebalancing modes on the
KafkaRebalance
custom resourcefull
: this mode runs a full rebalance moving replicas across all the brokers in the cluster. This is the default one if not specified.add-brokers
: after scaling up the cluster, this mode is used to move replicas to the newly added brokers specified in the custom resource.remove-brokers
: this mode is used to move replicas off the brokers that are going to be removed, before scaling down the cluster.
- Experimental KRaft mode (ZooKeeper-less Kafka) which can be enabled using the
UseKRaft
feature gate.
Important: Use it for development and testing only!
All changes can be found under the 0.29.0 milestone.
Changes, deprecations and removals
- Since the Cruise Control TLS sidecar has been removed, the related configuration options
.spec.cruiseControl.tlsSidecar
and.spec.cruiseControl.template.tlsSidecar
in the Kafka custom resource are now deprecated.
Maven artifacts
To test the Maven artifacts which are part of this release, use the staging repository by including following in your pom.xml
:
<repositories>
<repository>
<id>staging</id>
<url>https://oss.sonatype.org/content/repositories/iostrimzi-1169</url>
</repository>
</repositories>
Upgrading from Strimzi 0.28
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.28 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.28 is done!
For more details about the CRD upgrades, see the documentation.
0.28.0
Main changes since 0.27
- Add support for Kafka 3.1.0; remove Kafka 2.8.0 and 2.8.1
- Add support for
StrimziPodSet
resources (disabled by default through theUseStrimziPodSets
feature gate) - Update Open Policy Agent authorizer to 1.4.0 and add support for enabling metrics
- Support custom authentication mechanisms in Kafka listeners
- Intra-broker disk balancing using Cruise Control
- Add connector context to the default logging configuration in Kafka Connect and Kafka Mirror Maker 2
- Added the option
createBootstrapService
in the Kafka Spec to disable the creation of the bootstrap service for the Load Balancer Type Listener. It will save the cost of one load balancer resource, specially in the public cloud. - Added the
connectTimeoutSeconds
andreadTimeoutSeconds
options to OAuth authentication configuration. The default connect and read timeouts are set to 60 seconds (previously there was no timeout). Also addedgroupsClaim
andgroupsClaimDelimiter
options in the listener configuration of Kafka Spec to allow extracting group information from JWT token at authentication time, and making it available to the custom authorizer. These features are enabled by the updated Strimzi Kafka OAuth library (0.10.0). - Add support for disabling the FIPS mode in OpenJDK
- Fix renewing your own CA certificates #5466
- Update Strimzi Kafka Bridge to 0.21.4
- Update Cruise Control to 2.5.82
All changes can be found under the 0.28.0 milestone.
Changes, deprecations and removals
- The Strimzi Identity Replication Policy (class
io.strimzi.kafka.connect.mirror.IdentityReplicationPolicy
) is now deprecated and will be removed in the future.
Please update to Kafka's own Identity Replication Policy (classorg.apache.kafka.connect.mirror.IdentityReplicationPolicy
). - The
type
field inListenerStatus
has been deprecated and will be removed in the future.
Upgrading from Strimzi 0.27
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.28 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.28 is done!
For more details about the CRD upgrades, see the documentation.
0.28.0-rc1
Main changes since 0.27
- Add support for Kafka 3.1.0; remove Kafka 2.8.0 and 2.8.1
- Add support for
StrimziPodSet
resources (disabled by default through theUseStrimziPodSets
feature gate) - Update Open Policy Agent authorizer to 1.4.0 and add support for enabling metrics
- Support custom authentication mechanisms in Kafka listeners
- Intra-broker disk balancing using Cruise Control
- Add connector context to the default logging configuration in Kafka Connect and Kafka Mirror Maker 2
- Added the option
createBootstrapService
in the Kafka Spec to disable the creation of the bootstrap service for the Load Balancer Type Listener. It will save the cost of one load balancer resource, specially in the public cloud. - Added the
connectTimeoutSeconds
andreadTimeoutSeconds
options to OAuth authentication configuration. The default connect and read timeouts are set to 60 seconds (previously there was no timeout). Also addedgroupsClaim
andgroupsClaimDelimiter
options in the listener configuration of Kafka Spec to allow extracting group information from JWT token at authentication time, and making it available to the custom authorizer. These features are enabled by the updated Strimzi Kafka OAuth library (0.10.0). - Add support for disabling the FIPS mode in OpenJDK
- Fix renewing your own CA certificates #5466
- Update Strimzi Kafka Bridge to 0.21.4
- Update Cruise Control to 2.5.82
All changes can be found under the 0.28.0 milestone.
Changes, deprecations and removals
- The Strimzi Identity Replication Policy (class
io.strimzi.kafka.connect.mirror.IdentityReplicationPolicy
) is now deprecated and will be removed in the future.
Please update to Kafka's own Identity Replication Policy (classorg.apache.kafka.connect.mirror.IdentityReplicationPolicy
). - The
type
field inListenerStatus
has been deprecated and will be removed in the future.
Maven artifacts
To test the Maven artifacts which are part of this release, use the staging repository by including following in your pom.xml
:
<repositories>
<repository>
<id>staging</id>
<url>https://oss.sonatype.org/content/repositories/iostrimzi-1164</url>
</repository>
</repositories>
Upgrading from Strimzi 0.27
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.28 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.28 is done!
For more details about the CRD upgrades, see the documentation.