strimzi/strimzi-kafka-operator 0.30.0

on GitHub

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.