Releases: strimzi/strimzi-kafka-operator
0.37.0
Main changes since 0.36
This release contains the following new features and improvements:
- The
StableConnectIdentites
feature gate moves to a beta stage. By default, StrimziPodSets are used for Kafka Connect and Kafka Mirror Maker 2. If needed,StableConnectIdentites
can be disabled in the feature gates configuration in the Cluster Operator. - Support for the
ppc64le
platform - Added version fields to the
Kafka
custom resource status to track installation and upgrade state - Support for infinite auto-restarts of Kafka Connect and Kafka Mirror Maker 2 connectors
It also has several notable changes, deprecations, and removals:
- Removed support for OpenTracing:
- The
tracing.type: jaeger
configuration, inKafkaConnect
,KafkaMirrorMaker
,KafkaMirrorMaker2
andKafkaBridge
resources, is not supported anymore. - The OpenTelemetry-based tracing is the only available by using
tracing.type: opentelemetry
.
- The
- The default behavior of the Kafka Connect connector auto-restart has changed.
When the auto-restart feature is enabled inKafkaConnector
orKafkaMirrorMaker2
custom resources, it will now continue to restart the connectors indefinitely rather than stopping after 7 restarts, as previously.
If you want to use the original behavior, use the.spec.autoRestart.maxRestarts
option to configure the maximum number of restarts.
For example:apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaConnector metadata: labels: strimzi.io/cluster: my-connect name: echo-sink-connector spec: # ... autoRestart: enabled: true maxRestarts: 7 # ...
- The automatic configuration of Cruise Control CPU capacity has been changed in this release:
- There are three ways to configure Cruise Control CPU capacity values:
.spec.cruiseControl.brokerCapacity
(for all brokers).spec.cruiseControl.brokerCapacity.overrides
(per broker)- Kafka resource requests and limits (for all brokers).
- The precedence of which Cruise Control CPU capacity configuration is used has been changed.
- In previous Strimzi versions, the Kafka resource limit (if set) took precedence, regardless if any other CPU configurations were set.
- For example:
- (1) Kafka resource limits
- (2)
.spec.cruiseControl.brokerCapacity.overrides
- (3)
.spec.cruiseControl.brokerCapacity
- For example:
- This previous behavior was identified as a bug and was fixed in this Strimzi release.
- Going forward, the brokerCapacity overrides per broker take top precedence, then general brokerCapacity configuration, and then the Kafka resource requests, then the Kafka resource limits.
- For example:
- (1)
.spec.cruiseControl.brokerCapacity.overrides
- (2)
.spec.cruiseControl.brokerCapacity
- (3) Kafka resource requests
- (4) Kafka resource limits
- (1)
- When none of Cruise Control CPU capacity configurations mentioned above are configured, CPU capacity will be set to
1
.
as any override value configured in the.spec.cruiseControl
section of theKafka
custom resource.
- For example:
- There are three ways to configure Cruise Control CPU capacity values:
All changes can be found under the 0.37.0 milestone.
Upgrading from Strimzi 0.36.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:
Name | Image |
---|---|
Operators | quay.io/strimzi/operator@sha256:52f376e64b9b31d74162e26248c278e9bd301d2d8b4240ee5bcf780dfe2f8ef8 |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:38bbadcdb196a373e1698be890caa1dc01134ce91763d8f95c71768a117e1932 |
Apache Kafka 3.4.1 | quay.io/strimzi/kafka@sha256:1de6e073e8625a193fcfd11dd1a6717cc17596911c10bcebd792c00b08a7ebaf |
Apache Kafka 3.5.0 | quay.io/strimzi/kafka@sha256:2997ba1c169eb792a6004d7a41b674560515f3ea6e62ab8b9a1fdb747eab40c1 |
Apache Kafka 3.5.1 | quay.io/strimzi/kafka@sha256:dfeb1eb7b94107c443b6bc82fcfee7fcf782516c83c6fc64451fb6a7e2de74a6 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:5b821f6f3396002ffa7c5804391b627ff9da3b494b2777dde518c55c2b73cefc |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:5729f1f0511da95e64e358cfabb3980ad9a660af2968118a87d6755f5d652a67 |
Maven Builder | quay.io/strimzi/maven-builder@sha256:995be06a50b86c992fcee9f00e44f6a21c3406975e4e35802f10e88b72ffb9df |
0.37.0-rc1
Main changes since 0.36
This release contains the following new features and improvements:
- The
StableConnectIdentites
feature gate moves to a beta stage. By default, StrimziPodSets are used for Kafka Connect and Kafka Mirror Maker 2. If needed,StableConnectIdentites
can be disabled in the feature gates configuration in the Cluster Operator. - Support for the
ppc64le
platform - Added version fields to the
Kafka
custom resource status to track installation and upgrade state - Support for infinite auto-restarts of Kafka Connect and Kafka Mirror Maker 2 connectors
It also has several notable changes, deprecations, and removals:
- Removed support for OpenTracing:
- The
tracing.type: jaeger
configuration, inKafkaConnect
,KafkaMirrorMaker
,KafkaMirrorMaker2
andKafkaBridge
resources, is not supported anymore. - The OpenTelemetry-based tracing is the only available by using
tracing.type: opentelemetry
.
- The
- The default behavior of the Kafka Connect connector auto-restart has changed.
When the auto-restart feature is enabled inKafkaConnector
orKafkaMirrorMaker2
custom resources, it will now continue to restart the connectors indefinitely rather than stopping after 7 restarts, as previously.
If you want to use the original behavior, use the.spec.autoRestart.maxRestarts
option to configure the maximum number of restarts.
For example:apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaConnector metadata: labels: strimzi.io/cluster: my-connect name: echo-sink-connector spec: # ... autoRestart: enabled: true maxRestarts: 7 # ...
- The automatic configuration of Cruise Control CPU capacity has been changed in this release:
- There are three ways to configure Cruise Control CPU capacity values:
.spec.cruiseControl.brokerCapacity
(for all brokers).spec.cruiseControl.brokerCapacity.overrides
(per broker)- Kafka resource requests and limits (for all brokers).
- The precedence of which Cruise Control CPU capacity configuration is used has been changed.
- In previous Strimzi versions, the Kafka resource limit (if set) took precedence, regardless if any other CPU configurations were set.
- For example:
- (1) Kafka resource limits
- (2)
.spec.cruiseControl.brokerCapacity.overrides
- (3)
.spec.cruiseControl.brokerCapacity
- For example:
- This previous behavior was identified as a bug and was fixed in this Strimzi release.
- Going forward, the brokerCapacity overrides per broker take top precedence, then general brokerCapacity configuration, and then the Kafka resource requests, then the Kafka resource limits.
- For example:
- (1)
.spec.cruiseControl.brokerCapacity.overrides
- (2)
.spec.cruiseControl.brokerCapacity
- (3) Kafka resource requests
- (4) Kafka resource limits
- (1)
- When none of Cruise Control CPU capacity configurations mentioned above are configured, CPU capacity will be set to
1
.
as any override value configured in the.spec.cruiseControl
section of theKafka
custom resource.
- For example:
- There are three ways to configure Cruise Control CPU capacity values:
All changes can be found under the 0.37.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-1195/</url>
</repository>
</repositories>
Upgrading from Strimzi 0.36.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:
Name | Image |
---|---|
Operators | quay.io/strimzi/operator@sha256:52f376e64b9b31d74162e26248c278e9bd301d2d8b4240ee5bcf780dfe2f8ef8 |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:38bbadcdb196a373e1698be890caa1dc01134ce91763d8f95c71768a117e1932 |
Apache Kafka 3.4.1 | quay.io/strimzi/kafka@sha256:1de6e073e8625a193fcfd11dd1a6717cc17596911c10bcebd792c00b08a7ebaf |
Apache Kafka 3.5.0 | quay.io/strimzi/kafka@sha256:2997ba1c169eb792a6004d7a41b674560515f3ea6e62ab8b9a1fdb747eab40c1 |
Apache Kafka 3.5.1 | quay.io/strimzi/kafka@sha256:dfeb1eb7b94107c443b6bc82fcfee7fcf782516c83c6fc64451fb6a7e2de74a6 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:fefee252895e9f94756ed5c9ea71749e3fa89281df01bc55878a244ca7d17697 |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:5729f1f0511da95e64e358cfabb3980ad9a660af2968118a87d6755f5d652a67 |
Maven Builder | quay.io/strimzi/maven-builder@sha256:995be06a50b86c992fcee9f00e44f6a21c3406975e4e35802f10e88b72ffb9df |
0.36.1
Main changes since 0.36.0
- Support for Apache Kafka 3.5.1
- Fix Grafana Dashboards in the Helm Chart
- Fix issues with 2-node ZooKeeper deployment
- Documentation fixes
All changes can be found under the 0.36.1 milestone.
Upgrading from Strimzi 0.36.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:
Name | Image |
---|---|
Operators | quay.io/strimzi/operator@sha256:e9e03b31007c0f9b67a6a33e6b644e8c1ba35bd9976804ee3d22a04e4bf511b1 |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:a0da6a48b5bcbff355365f07df2d99ef6443d22c5690495f10a6417e761b3799 |
Apache Kafka 3.4.1 | quay.io/strimzi/kafka@sha256:9f35f40be3d47b0cb1f6628f7ffd9c6a687ab9f564829f341dd66fd0759c064f |
Apache Kafka 3.5.0 | quay.io/strimzi/kafka@sha256:67c2b563a65c85c9393608f9af7eaf12ea48dcc0ef5f726d51f27273a3845186 |
Apache Kafka 3.5.1 | quay.io/strimzi/kafka@sha256:ea35817ff1ef295c682d70562f209ef658fcd87c61f467a4549d7a2f39e71700 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:fefee252895e9f94756ed5c9ea71749e3fa89281df01bc55878a244ca7d17697 |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:5ff9fc7d0b7b694875ad0150fc787c582d42da3b4864d807ee8a6524e47b0e4e |
Maven Builder | quay.io/strimzi/maven-builder@sha256:2a469b40122027b981914db5b5c102be48280e039c3089963422c181174af226 |
0.36.1-rc1
Main changes since 0.36.0
- Support for Apache Kafka 3.5.1
- Fix Grafana Dashboards in the Helm Chart
- Fix issues with 2-node ZooKeeper deployment
- Documentation fixes
All changes can be found under the 0.36.1 milestone.
Maven artifacts
To test the Maven artifacts which 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-1192/</url>
</repository>
</repositories>
Upgrading from Strimzi 0.36.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:
Name | Image |
---|---|
Operators | quay.io/strimzi/operator@sha256:e9e03b31007c0f9b67a6a33e6b644e8c1ba35bd9976804ee3d22a04e4bf511b1 |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:a0da6a48b5bcbff355365f07df2d99ef6443d22c5690495f10a6417e761b3799 |
Apache Kafka 3.4.1 | quay.io/strimzi/kafka@sha256:9f35f40be3d47b0cb1f6628f7ffd9c6a687ab9f564829f341dd66fd0759c064f |
Apache Kafka 3.5.0 | quay.io/strimzi/kafka@sha256:67c2b563a65c85c9393608f9af7eaf12ea48dcc0ef5f726d51f27273a3845186 |
Apache Kafka 3.5.1 | quay.io/strimzi/kafka@sha256:ea35817ff1ef295c682d70562f209ef658fcd87c61f467a4549d7a2f39e71700 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:fefee252895e9f94756ed5c9ea71749e3fa89281df01bc55878a244ca7d17697 |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:5ff9fc7d0b7b694875ad0150fc787c582d42da3b4864d807ee8a6524e47b0e4e |
Maven Builder | quay.io/strimzi/maven-builder@sha256:2a469b40122027b981914db5b5c102be48280e039c3089963422c181174af226 |
0.36.0
Main changes since 0.35
This release contains the following new features and improvements:
- Add support for Apache Kafka 3.4.1 and 3.5.0, and remove support for 3.3.1 and 3.3.2
- Enable SCRAM-SHA authentication in KRaft mode (supported in Apache Kafka 3.5.0 and newer)
- Add support for insecure flag in Maven artifacts in Kafka Connect Build
- Improve Kafka rolling update to avoid rolling broker in log recovery
- Added support for Kafka Exporter topic exclude and consumer group exclude parameters
- Add support for Kafka node pools according to Strimzi Proposal #50
- Add support for Unidirectional Topic Operator according to Strimzi Proposal #51
- Fixed ordering of JVM performance options #8579
It also has several notable changes, deprecations, and removals:
- From Strimzi 0.36.0 on, we support only Kubernetes 1.21 and newer.
Kubernetes 1.19 and 1.20 are not supported anymore. - Enabling the
UseKRaft
feature gate is now possible only together with theKafkaNodePools
feature gate.
To deploy a Kafka cluster in the KRaft mode, you have to use theKafkaNodePool
resources. - The Helm Chart repository at
https://strimzi.io/charts/
is now deprecated.
Please use the Helm Chart OCI artifacts from our Helm Chart OCI repository instead. - Option
customClaimCheck
of 'oauth' authentication which relies on JsonPath changed the handling of equal comparison againstnull
as the behaviour was buggy and is now fixed in the updated version of JsonPath library OAuth #196
All changes can be found under the 0.36.0 milestone.
Upgrading from Strimzi 0.35.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:
Name | Image |
---|---|
Operator | quay.io/strimzi/operator@sha256:e18d4a9c4b6d91ddac2207bedd792f695c054ed3692727872b36b6435cd95f7b |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:03e59830d18b7816be25ca83b09542b1215b251eee281609d10fe137737ee6da |
Apache Kafka 3.4.1 | quay.io/strimzi/kafka@sha256:0241d35e31c1116d5b0b81d611a50546990703e00ebfaadbe6f5af7c2fd6a9bd |
Apache Kafka 3.5.0 | quay.io/strimzi/kafka@sha256:85865eb4403d0e8644cd04f3dba9f9527f56f546822ce0bed370260167490951 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:3c10093c460f91f39d77a301c6f66698c7c3833b0fa69262e4114e6293d50e77 |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:5ff9fc7d0b7b694875ad0150fc787c582d42da3b4864d807ee8a6524e47b0e4e |
Maven Builder | quay.io/strimzi/maven-builder@sha256:78ca90e6903ec44b2d2bfbc8c73c44aa7bf7007b7659622d38e1191d28a0d037 |
0.36.0-rc1
Main changes since 0.35
This release contains the following new features and improvements:
- Add support for Apache Kafka 3.4.1 and 3.5.0, and remove support for 3.3.1 and 3.3.2
- Enable SCRAM-SHA authentication in KRaft mode (supported in Apache Kafka 3.5.0 and newer)
- Add support for insecure flag in Maven artifacts in Kafka Connect Build
- Improve Kafka rolling update to avoid rolling broker in log recovery
- Added support for Kafka Exporter topic exclude and consumer group exclude parameters
- Add support for Kafka node pools according to Strimzi Proposal #50
- Add support for Unidirectional Topic Operator according to Strimzi Proposal #51
- Fixed ordering of JVM performance options #8579
It also has several notable changes, deprecations, and removals:
- From Strimzi 0.36.0 on, we support only Kubernetes 1.21 and newer.
Kubernetes 1.19 and 1.20 are not supported anymore. - Enabling the
UseKRaft
feature gate is now possible only together with theKafkaNodePools
feature gate.
To deploy a Kafka cluster in the KRaft mode, you have to use theKafkaNodePool
resources. - The Helm Chart repository at
https://strimzi.io/charts/
is now deprecated.
Please use the Helm Chart OCI artifacts from our Helm Chart OCI repository instead. - Option
customClaimCheck
of 'oauth' authentication which relies on JsonPath changed the handling of equal comparison againstnull
as the behaviour was buggy and is now fixed in the updated version of JsonPath library OAuth #196
All changes can be found under the 0.36.0 milestone.
Maven artifacts
To test the Maven artifacts which 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-1189/</url>
</repository>
</repositories>
Upgrading from Strimzi 0.35.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:
Name | Image |
---|---|
Operators | quay.io/strimzi/operator@sha256:e18d4a9c4b6d91ddac2207bedd792f695c054ed3692727872b36b6435cd95f7b |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:03e59830d18b7816be25ca83b09542b1215b251eee281609d10fe137737ee6da |
Apache Kafka 3.4.1 | quay.io/strimzi/kafka@sha256:0241d35e31c1116d5b0b81d611a50546990703e00ebfaadbe6f5af7c2fd6a9bd |
Apache Kafka 3.5.0 | quay.io/strimzi/kafka@sha256:85865eb4403d0e8644cd04f3dba9f9527f56f546822ce0bed370260167490951 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:3c10093c460f91f39d77a301c6f66698c7c3833b0fa69262e4114e6293d50e77 |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:5ff9fc7d0b7b694875ad0150fc787c582d42da3b4864d807ee8a6524e47b0e4e |
Maven Builder | quay.io/strimzi/maven-builder@sha256:78ca90e6903ec44b2d2bfbc8c73c44aa7bf7007b7659622d38e1191d28a0d037 |
0.35.1
Main changes since 0.35.0
Bug Fixes
- Update Fabric8 Kubernetes Client to 6.7.0
Upgrading from Strimzi 0.35.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:
Name | Image |
---|---|
Operators | quay.io/strimzi/operator@sha256:06a94a3021cf028ccc1a49271f35f79216029e344536e664f196c1725ff2c663 |
Apache Kafka 3.3.1 | quay.io/strimzi/kafka@sha256:4de4874a7b722ad813f4dcc58acf509527bca0609999b81e70d81e3b38534d9d |
Apache Kafka 3.3.2 | quay.io/strimzi/kafka@sha256:0d910e7138cb49e1cd8cd84cef88bce35698b93ddd683a3398f1d485a3162693 |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:54c6b25b31f51ef401c1b6e2a1b27432911e819bf3e502e05186f01be3f798e5 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:d6be183e492f8f88157ab9fe0af53950df8b6711a8a8c33da465de6064f6f86e |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:39778b90c2b2afc30261e4ad5135805e1a10a2b60e2e53108fb9f80487f1208a |
Maven Builder | quay.io/strimzi/maven-builder@sha256:88a79eff3b3a386880a630658964b7754caed9e99dd6e645a4c0d23d0fdb47ee |
0.35.1-rc1
Main changes since 0.35.0
Bug Fixes
- Update Fabric8 Kubernetes Client to 6.7.0
Maven artifacts
To test the Maven artifacts which 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-1182/</url>
</repository>
</repositories>
Upgrading from Strimzi 0.35.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:
Name | Image |
---|---|
Operators | quay.io/strimzi/operator@sha256:06a94a3021cf028ccc1a49271f35f79216029e344536e664f196c1725ff2c663 |
Apache Kafka 3.3.1 | quay.io/strimzi/kafka@sha256:4de4874a7b722ad813f4dcc58acf509527bca0609999b81e70d81e3b38534d9d |
Apache Kafka 3.3.2 | quay.io/strimzi/kafka@sha256:0d910e7138cb49e1cd8cd84cef88bce35698b93ddd683a3398f1d485a3162693 |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:54c6b25b31f51ef401c1b6e2a1b27432911e819bf3e502e05186f01be3f798e5 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:d6be183e492f8f88157ab9fe0af53950df8b6711a8a8c33da465de6064f6f86e |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:39778b90c2b2afc30261e4ad5135805e1a10a2b60e2e53108fb9f80487f1208a |
Maven Builder | quay.io/strimzi/maven-builder@sha256:88a79eff3b3a386880a630658964b7754caed9e99dd6e645a4c0d23d0fdb47ee |
0.35.0
Main changes since 0.34
New features and improvements
- Move feature gate
UseStrimziPodSets
to GA and remove support for StatefulSets - Remove support for JMX Trans
- Redesigned the Cluster and User Operator configuration to make it more efficient and flexible
- Allow multiple imagePullSecrets in the Strimzi Helm chart
- Add flag to load Grafana dashboards from Helm Chart
All changes can be found under the 0.35.0 milestone.
Upgrading from Strimzi 0.34.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:
Name | Image |
---|---|
Operators | quay.io/strimzi/operator@sha256:59df996575607fc4fe348c54904b782a5691688a66c71abeca2bf127a2433180 |
Apache Kafka 3.3.1 | quay.io/strimzi/kafka@sha256:2249dad688c10237cbaad20ad5575561ac844429acba2a85cd526f11ee6707c6 |
Apache Kafka 3.3.2 | quay.io/strimzi/kafka@sha256:56e2fc1c2a4c8aaa517478f228ab9ea81c9a8f990b86bac2c0896338e3f4656c |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:cab70fa2bb9b731209ed1c4829e1e8a6ac37bff62b6443b79c9ec744b02c9256 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:d6be183e492f8f88157ab9fe0af53950df8b6711a8a8c33da465de6064f6f86e |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:39778b90c2b2afc30261e4ad5135805e1a10a2b60e2e53108fb9f80487f1208a |
Maven Builder | quay.io/strimzi/maven-builder@sha256:2ee5d1a63dc56c31f9c30755bb7564952752bcd39c45d00dfea42c09673eaa0e |
0.35.0-rc1
Main changes since 0.34
New features and improvements
- Move feature gate
UseStrimziPodSets
to GA and remove support for StatefulSets - Remove support for JMX Trans
- Redesigned the Cluster and User Operator configuration to make it more efficient and flexible
- Allow multiple imagePullSecrets in the Strimzi Helm chart
- Add flag to load Grafana dashboards from Helm Chart
All changes can be found under the 0.35.0 milestone.
Maven artifacts
To test the Maven artifacts which 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-1180/</url>
</repository>
</repositories>
Upgrading from Strimzi 0.34.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:
Name | Image |
---|---|
Operators | quay.io/strimzi/operator@sha256:59df996575607fc4fe348c54904b782a5691688a66c71abeca2bf127a2433180 |
Apache Kafka 3.3.1 | quay.io/strimzi/kafka@sha256:2249dad688c10237cbaad20ad5575561ac844429acba2a85cd526f11ee6707c6 |
Apache Kafka 3.3.2 | quay.io/strimzi/kafka@sha256:56e2fc1c2a4c8aaa517478f228ab9ea81c9a8f990b86bac2c0896338e3f4656c |
Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:cab70fa2bb9b731209ed1c4829e1e8a6ac37bff62b6443b79c9ec744b02c9256 |
Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:98eb7542e3ff4e10043040acff7a90aa5fd87ff1ea0cac8491f66b1bbdf072dd |
Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:39778b90c2b2afc30261e4ad5135805e1a10a2b60e2e53108fb9f80487f1208a |
Maven Builder | quay.io/strimzi/maven-builder@sha256:2ee5d1a63dc56c31f9c30755bb7564952752bcd39c45d00dfea42c09673eaa0e |