Update Helm release strimzi-kafka-operator to v1.1.0

Share
Update Helm release strimzi-kafka-operator to v1.1.0
Photo by Growtika / Unsplash

No problems deploying Strimzi Apache Kafka cluster to Proxmox VE K3s Kubernetes cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach with dependency update facilitated by Mend's Renovate Bot.

This MR contains the following updates:

Package Update Change
strimzi-kafka-operator (source) minor 1.0.11.1.0

Release Notes

strimzi/strimzi-kafka-operator (strimzi-kafka-operator)

v1.1.0

Compare Source

  • Allow failed KafkaConnectors to be stopped and reject pausing of failed connectors since this operation is not supported by Kafka Connect
  • Add support for Apache Kafka 4.3.0 and 4.2.1
  • Remove support for Kafka 4.1.x
  • Reconcile Cruise Control before Entity Operator when both are enabled.
  • New Cluster operator configuration option STRIMZI_PKCS12_KEYSTORE_GENERATION to disable generating PKCS12 stores in CA and Kafka user Secret resources.
  • Support for Gateway API-based type: tlsroute listener
  • Support for dependency scope configuration of Maven artifacts in Kafka Connect Build
  • Support for configuring per-broker listener annotation and label templates.
  • Improved support for custom Apache Kafka versions
  • Add UseBackgroundPodDeletion feature gate (alpha, disabled by default) to use background deletion propagation when deleting pods during rolling updates.
  • Strimzi Drain Cleaner updated to 1.6.0 (included in the Strimzi installation files)
  • Strimzi Access Operator updated to 0.3.0 - included in Strimzi installation files, examples, and documentation
  • KafkaBridge and KafkaMirrorMaker2 now use PEM files instead of P12/JKS for TLS authentication and TLS truststore. PEM files are accessed directly from secrets using KubernetesSecretConfigProvider.
  • It's now possible to configure mTLS validityDays and renewalDays for each KafkaUser
Major changes, deprecations, and removals
  • The entity-operator healthcheck port names have been renamed from healthcheck to healthcheck-to (topic-operator) and healthcheck-uo (user-operator) to avoid duplicate port name warnings in Kubernetes. If you reference these port names in custom PodMonitor, ServiceMonitor, NetworkPolicy, or similar resources, you will need to update them.

Read more

Me on Mastodon - This link is here for verification purposes.