strimzi-kafka-operator | Kubernetes Ecosystem Directory

Bot releases are hidden (Show)

strimzi-kafka-operator - 0.33.2-rc1

Published by scholzj over 1 year ago

Main changes since 0.33.1

⚠️ 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!

Bug Fixes

Support for Kafka 3.4.0 which fixes CVE-2023-25194
Fix RBAC files in standalone User OPerator installation files

strimzi-kafka-operator - 0.33.1

Published by scholzj over 1 year ago

Main changes since 0.33.0

⚠️ 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!

Bug Fixes

Remove the Lease resource from installation files

strimzi-kafka-operator - 0.33.1-rc1

Published by scholzj over 1 year ago

Main changes since 0.33.0

⚠️ 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!

Bug Fixes

Remove the Lease resource from installation files

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-1170/</url>
    </repository>
  </repositories>

strimzi-kafka-operator - 0.33.0

Published by scholzj over 1 year ago

Main changes since 0.32

⚠️ 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!

New features and improvements

Add support for Kafka 3.3.2
Support loadBalancerClass attribute in listeners with type loadbalancer
Support for automatically restarting failed Connect or Mirror Maker 2 connectors
Redesign of Strimzi User Operator to improve its scalability
Use Java 17 as the runtime for all containers and language level for all modules except api, crd-generator, crd-annotations, and test
Improved FIPS (Federal Information Processing Standards) support
Moved from using the Jaeger exporter to OTLP exporter by default
Kafka Exporter support for Recreate deployment strategy
ImageStream validation for Kafka Connect builds on OpenShift
Support for configuring the metadata for the Role / RoleBinding of Entity Operator
Add liveness and readiness probes specifically for nodes running in KRaft combined mode
Upgrade HTTP bridge to latest 0.24.0 release

Known issues

The TLS passthrough feature of the Ingress-NGINX Controller for Kubernetes is not compatible with some TLS features supported by Java 17 such as the session tickets extension.
If you use type: 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"
  # ...
```
For more details, see kubernetes/ingress-nginx#9540.

Notable changes, deprecations, and removals

The 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.
The default length of any new SCRAM-SHA-512 passwords will be 32 characters instead of 12 characters used in the previous Strimzi versions. Existing passwords will not be affected by this change until they are regenerated (for example because the user secret is deleted). If you want to keep using the original password length, you can set it using the 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"
```
In previous versions, the 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.
Support for JmxTrans in Strimzi is deprecated. It is currently planned to be removed in Strimzi 0.35.0.
Support for 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.
When OpenTelemetry is enabled for tracing, starting from this release, the operator configures the OTLP exporter instead of the Jaeger one by default. The Jaeger exporter is even not included in the Kafka images anymore, so if you want to use it you have to add the binary by yourself. The 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.

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

strimzi-kafka-operator - 0.33.0-rc1

Published by scholzj over 1 year ago

Main changes since 0.32

⚠️ 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!

New features and improvements

Add support for Kafka 3.3.2
Support loadBalancerClass attribute in listeners with type loadbalancer
Support for automatically restarting failed Connect or Mirror Maker 2 connectors
Redesign of Strimzi User Operator to improve its scalability
Use Java 17 as the runtime for all containers and language level for all modules except api, crd-generator, crd-annotations, and test
Improved FIPS (Federal Information Processing Standards) support
Moved from using the Jaeger exporter to OTLP exporter by default
Kafka Exporter support for Recreate deployment strategy
ImageStream validation for Kafka Connect builds on OpenShift
Support for configuring the metadata for the Role / RoleBinding of Entity Operator
Add liveness and readiness probes specifically for nodes running in KRaft combined mode
Upgrade HTTP bridge to latest 0.24.0 release

Notable changes, deprecations, and removals

The 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.
The default length of any new SCRAM-SHA-512 passwords will be 32 characters instead of 12 characters used in the previous Strimzi versions. Existing passwords will not be affected by this change until they are regenerated (for example because the user secret is deleted). If you want to keep using the original password length, you can set it using the 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"
```
In previous versions, the 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.
Support for JmxTrans in Strimzi is deprecated. It is currently planned to be removed in Strimzi 0.35.0.
Support for 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.
When OpenTelemetry is enabled for tracing, starting from this release, the operator configures the OTLP exporter instead of the Jaeger one by default. The Jaeger exporter is even not included in the Kafka images anymore, so if you want to use it you have to add the binary by yourself. The 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.

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-1169/</url>
    </repository>
  </repositories>

Upgrading from Strimzi 0.32.0

See the documentation for upgrade instructions.

Upgrading from Strimzi 0.22 or earlier

strimzi-kafka-operator - 0.32.0

Published by scholzj almost 2 years 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

strimzi-kafka-operator - 0.32.0-rc1

Published by scholzj almost 2 years 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.

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-1204</url>
    </repository>
  </repositories>

Upgrading from Strimzi 0.31.0

See the documentation for upgrade instructions.

Upgrading from Strimzi 0.22 or earlier

strimzi-kafka-operator - 0.31.1

Published by scholzj about 2 years ago

Main changes since 0.31.0

Strimzi 0.31 is the last version of Strimzi with support for Kubernetes 1.16, 1.17 and 1.18!

Kafka 3.1.2 and 3.2.3 (fixes CVE-2022-34917)
Make sasl.server.max.receive.size broker option user configurable
Documentation improvements
Configuring number of operator replicas through the Strimzi Helm Chart
Update Strimzi Kafka Bridge to 0.22.1

All changes can be found under the 0.31.1 milestone.

Upgrading from Strimzi 0.30 or 0.31.0

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.

strimzi-kafka-operator - 0.31.1-rc1

Published by scholzj about 2 years ago

Main changes since 0.31.0

This is the last version of Strimzi with support for Kubernetes 1.16, 1.17 and 1.18!

Kafka 3.1.2 and 3.2.3 (fixes CVE-2022-34917)
Make sasl.server.max.receive.size broker option user configurable
Documentation improvements
Configuring number of operator replicas through the Strimzi Helm Chart
Update Strimzi Kafka Bridge to 0.22.1

All changes can be found under the 0.31.1 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-1188</url>
    </repository>
  </repositories>

Upgrading from Strimzi 0.30 or 0.31.0

See the documentation for upgrade instructions.

Upgrading from Strimzi 0.22 or earlier

For more details about the CRD upgrades, see the documentation.

strimzi-kafka-operator - 0.31.0

Published by scholzj about 2 years ago

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.

Upgrading from Strimzi 0.30

See the documentation for upgrade instructions.

Upgrading from Strimzi 0.22 or earlier

For more details about the CRD upgrades, see the documentation.

strimzi-kafka-operator - 0.31.0-rc2

Published by scholzj about 2 years ago

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

For more details about the CRD upgrades, see the documentation.

strimzi-kafka-operator - 0.31.0-rc1

Published by scholzj about 2 years ago

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

For more details about the CRD upgrades, see the documentation.

strimzi-kafka-operator - 0.30.0

Published by scholzj about 2 years ago

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 experimental UseKRaft 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.

strimzi-kafka-operator - 0.30.0-rc2

Published by scholzj over 2 years ago

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.

strimzi-kafka-operator - 0.30.0-rc1

Published by scholzj over 2 years ago

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 experimental UseKRaft 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.

strimzi-kafka-operator - 0.29.0

Published by scholzj over 2 years ago

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 resource
- full: 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.

strimzi-kafka-operator - 0.29.0-rc2

Published by scholzj over 2 years ago

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>

strimzi-kafka-operator - 0.29.0-rc1

Published by scholzj over 2 years ago

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 resource
- full: 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.

strimzi-kafka-operator - 0.28.0

Published by scholzj over 2 years ago

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 the UseStrimziPodSets 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 and readTimeoutSeconds options to OAuth authentication configuration. The default connect and read timeouts are set to 60 seconds (previously there was no timeout). Also added groupsClaim and groupsClaimDelimiter 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 (class org.apache.kafka.connect.mirror.IdentityReplicationPolicy).
The type field in ListenerStatus 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.

strimzi-kafka-operator - 0.28.0-rc1

Published by scholzj over 2 years ago

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 the UseStrimziPodSets 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 and readTimeoutSeconds options to OAuth authentication configuration. The default connect and read timeouts are set to 60 seconds (previously there was no timeout). Also added groupsClaim and groupsClaimDelimiter 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 (class org.apache.kafka.connect.mirror.IdentityReplicationPolicy).
The type field in ListenerStatus 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.