Apache Kafka® running on Kubernetes
⚠️ Important: Strimzi 0.34.0 supports only Kubernetes 1.19 and newer! Kubernetes versions 1.16, 1.17 and 1.18 are not supported anymore since Strimzi 0.32.
⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!
StableConnectIdentities)All changes can be found under the 0.34.0 milestone.
See the documentation for upgrade instructions.
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.
The following container images are part of this release:
| Name | Image |
|---|---|
| Operators | quay.io/strimzi/operator@sha256:f4ee3ca482a2dd19785f59634578a0850273444c1173a5699a99cf02f3a018fe |
| Apache Kafka 3.3.1 | quay.io/strimzi/kafka@sha256:1da35fd7b36b113d1343e254fdc6efd97ca8660cc7977d8985aa3a3547d5ebb1 |
| Apache Kafka 3.3.2 | quay.io/strimzi/kafka@sha256:1ace2cc0db9653ac1b388477fa56c3c1cd97c7b3846eba3c7824dc58ea179476 |
| Apache Kafka 3.4.0 | quay.io/strimzi/kafka@sha256:37cf8d0fea1d2078511920190a72b49977ff4047b6ecbfed6b394c6f9e1e2ff0 |
| Strimzi Bridge | quay.io/strimzi/kafka-bridge@sha256:51babca0f7a328f4db005c6a16daa8ac4a4306c46fe3ca89382919134aa09179 |
| JMX Trans | quay.io/strimzi/jmxtrans@sha256:62272e8a03da2144340bd7267f7a824d1ed70f4f3e30dc7aadfba9ee1b9baf76 |
| Kaniko executor | quay.io/strimzi/kaniko-executor@sha256:dc27d8aeb851245c79fb7276febe98769cc098d678bea096b338caaaf111dd27 |
| Maven Builder | quay.io/strimzi/maven-builder@sha256:f781b6b857d437c2de62585462e97b9fae357912c9f6711c1df39f431278878d |
⚠️ Important: Strimzi 0.34.0 supports only Kubernetes 1.19 and newer! Kubernetes versions 1.16, 1.17 and 1.18 are not supported anymore since Strimzi 0.32.
⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!
StableConnectIdentities)All changes can be found under the 0.34.0 milestone.
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-1177/</url>
</repository>
</repositories>
See the documentation for upgrade instructions.
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.
⚠️ Important: Strimzi 0.33.2 supports only Kubernetes 1.19 and newer! Kubernetes versions 1.16, 1.17 and 1.18 are not supported anymore since Strimzi 0.32.
⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!
⚠️ Important: Strimzi 0.33.2 supports only Kubernetes 1.19 and newer! Kubernetes versions 1.16, 1.17 and 1.18 are not supported anymore since Strimzi 0.32.
⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!
⚠️ Important: Strimzi 0.33.1 supports only Kubernetes 1.19 and newer! Kubernetes versions 1.16, 1.17 and 1.18 are not supported anymore since Strimzi 0.32.
⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!
Lease resource from installation files⚠️ Important: Strimzi 0.33.1 supports only Kubernetes 1.19 and newer! Kubernetes versions 1.16, 1.17 and 1.18 are not supported anymore since Strimzi 0.32.
⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!
Lease resource from installation filesTo 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-1170/</url>
</repository>
</repositories>
⚠️ Important: Strimzi 0.33.0 supports only Kubernetes 1.19 and newer! Kubernetes versions 1.16, 1.17 and 1.18 are not supported anymore since Strimzi 0.32.
⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!
loadBalancerClass attribute in listeners with type loadbalancer
api, crd-generator, crd-annotations, and test
Recreate deployment strategyImageStream validation for Kafka Connect builds on OpenShifttype: ingress listener with enabled mTLS authentication, we recommend you to test if your clients are affected or not.
If needed, you can also disable the session ticket extension in the Kafka brokers in your Kafka custom resource by setting the jdk.tls.server.enableSessionTicketExtension Java system property to false:
apiVersion: kafka.strimzi.io/v1beta2
kind: Kafka
metadata:
# ...
spec:
# ...
kafka:
jvmOptions:
javaSystemProperties:
- name: jdk.tls.server.enableSessionTicketExtension
value: "false"
# ...
UseStrimziPodSet feature gate will move to GA in Strimzi 0.35. Support for StatefulSets will be removed from Strimzi right after the 0.34 release. Please use the Strimzi 0.33 release to test StrimziPodSets in your environment and report any major or blocking issues before the StatefulSet support is removed.STRIMZI_SCRAM_SHA_PASSWORD_LENGTH environment variable in .spec.entityOperator.template.userOperatorContainer.env in the Kafka custom resource or in the
Deployment of the standalone User Operator.
userOperatorContainer:
env:
- name: STRIMZI_SCRAM_SHA_PASSWORD_LENGTH
value: "12"
ssl.secure.random.implementation option in Kafka brokers was always set to SHA1PRNG. From Strimzi 0.33 on, it is using the default SecureRandom implementation from the Java Runtime. If you want to keep using SHA1PRNG as your SecureRandom, you can configure it in .spec.kafka.config in your Kafka custom resource.type: jaeger tracing based on Jaeger clients and OpenTracing API was deprecated in the Strimzi 0.31 release. As the Jaeger clients are retired and the OpenTracing project is archived, we cannot guarantee their support for future versions. In Strimzi 0.32 and 0.33, we added support for OpenTelemetry tracing as a replacement. If possible, we will maintain the support for type: jaeger tracing until June 2023 and remove it afterward. Please migrate to OpenTelemetry as soon as possible.OTEL_EXPORTER_OTLP_ENDPOINT environment variable has to be used instead of the OTEL_EXPORTER_JAEGER_ENDPOINT in order to specify the OTLP endpoint to send traces to. If you are using Jaeger as the backend system for tracing, you need to have 1.35 release at least which is the first one exposing an OTLP endpoint.All changes can be found under the 0.33.0 milestone.
See the documentation for upgrade instructions.
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.
⚠️ Important: Strimzi 0.33.0 supports only Kubernetes 1.19 and newer! Kubernetes versions 1.16, 1.17 and 1.18 are not supported anymore since Strimzi 0.32.
⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!
loadBalancerClass attribute in listeners with type loadbalancer
api, crd-generator, crd-annotations, and test
Recreate deployment strategyImageStream validation for Kafka Connect builds on OpenShiftUseStrimziPodSet feature gate will move to GA in Strimzi 0.35. Support for StatefulSets will be removed from Strimzi right after the 0.34 release. Please use the Strimzi 0.33 release to test StrimziPodSets in your environment and report any major or blocking issues before the StatefulSet support is removed.STRIMZI_SCRAM_SHA_PASSWORD_LENGTH environment variable in .spec.entityOperator.template.userOperatorContainer.env in the Kafka custom resource or in the
Deployment of the standalone User Operator.
userOperatorContainer:
env:
- name: STRIMZI_SCRAM_SHA_PASSWORD_LENGTH
value: "12"
ssl.secure.random.implementation option in Kafka brokers was always set to SHA1PRNG. From Strimzi 0.33 on, it is using the default SecureRandom implementation from the Java Runtime. If you want to keep using SHA1PRNG as your SecureRandom, you can configure it in .spec.kafka.config in your Kafka custom resource.type: jaeger tracing based on Jaeger clients and OpenTracing API was deprecated in the Strimzi 0.31 release. As the Jaeger clients are retired and the OpenTracing project is archived, we cannot guarantee their support for future versions. In Strimzi 0.32 and 0.33, we added support for OpenTelemetry tracing as a replacement. If possible, we will maintain the support for type: jaeger tracing until June 2023 and remove it afterward. Please migrate to OpenTelemetry as soon as possible.OTEL_EXPORTER_OTLP_ENDPOINT environment variable has to be used instead of the OTEL_EXPORTER_JAEGER_ENDPOINT in order to specify the OTLP endpoint to send traces to. If you are using Jaeger as the backend system for tracing, you need to have 1.35 release at least which is the first one exposing an OLTP endpoint.All changes can be found under the 0.33.0 milestone.
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-1169/</url>
</repository>
</repositories>
See the documentation for upgrade instructions.
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.
⚠️ 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!
ControlPlaneListener feature gate moves to GAAll 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.
See the documentation for upgrade instructions.
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.
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!
ControlPlaneListener feature gate moves to GAAll changes can be found under the 0.32.0 milestone.
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-1204</url>
</repository>
</repositories>
See the documentation for upgrade instructions.
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.