strimzi/strimzi-kafka-operator 0.37.0

on GitHub

⚠️ Important: Strimzi 0.37.0 supports only Kubernetes 1.21 and newer! Kubernetes versions 1.19 and 1.20 are not supported anymore since Strimzi 0.36.

⚠️ Important: Direct upgrade from Strimzi 0.22 or earlier is not supported anymore!

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, in KafkaConnect, KafkaMirrorMaker, KafkaMirrorMaker2 and KafkaBridge resources, is not supported anymore.
  • The OpenTelemetry-based tracing is the only available by using tracing.type: opentelemetry.
• The default behavior of the Kafka Connect connector auto-restart has changed.
  When the auto-restart feature is enabled in KafkaConnector or KafkaMirrorMaker2 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
  • 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
    • 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 the Kafka custom resource.

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: