feat(charts): update helm release strimzi-kafka-operator to v0.32.0

[renovate]

This PR contains the following updates:

Package	Update	Change
strimzi-kafka-operator (source)	minor	0.31.1 -> 0.32.0

---

Release Notes

strimzi/strimzi-kafka-operator

v0.32.0

Compare Source

• Add support for Kafka 3.3.1 and remove support for Kafka 3.1.0, 3.1.1, and 3.1.2
• Update Open Policy Agent (OPA) Authorizer to 1.5.0
• 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
  • Kafka Connect, Mirror Maker, Mirror Maker 2 and Strimzi Bridge can be configured to use OpenTelemetry
  • Using Jaeger exporter by default for backward compatibility
• Updated JMX Exporter dependency to 0.17.2
• ZookeeperRoller considers unready pods
• Support multiple operations per ACLRule
• Upgrade Vert.x to 4.3.4
• Add cluster-ip listener. We can use it with a tcp port configuration in an ingress controller to expose kafka with an optional tls encryption and a single LoadBalancer.
• Update Strimzi OAuth library to 0.11.0

Changes, deprecations and removals

• From 0.32.0 on, Strimzi supports only Kubernetes version 1.19 and newer.
• A connector or task failing triggers a 'NotReady' condition to be added to the KafkaConnector CR status. This is different from previous versions where the CR would report 'Ready' even if the connector or a task had failed.
• The ClusterRole from file 020-ClusterRole-strimzi-cluster-operator-role.yaml was split into two separate roles:
  • The original strimzi-cluster-operator-namespaced ClusterRole in the file 020-ClusterRole-strimzi-cluster-operator-role.yaml contains the rights related to the resources created based on some Strimzi custom resources.
  • The new strimzi-cluster-operator-watched ClusterRole in the file 023-ClusterRole-strimzi-cluster-operator-role.yaml contains the rights required to watch and manage the Strimzi custom resources.
    When deploying the Strimzi Cluster Operator as cluster-wide, the strimzi-cluster-operator-watched ClusterRole needs to be always granted at the cluster level.
    But the strimzi-cluster-operator-namespaced ClusterRole might be granted only for the namespaces where any custom resources are created.
• The ControlPlaneListener feature gate moves to GA.
  Direct upgrade from Strimzi 0.22 or earlier is not possible anymore.
  You have to upgrade first to one of the Strimzi versions between 0.22 and 0.32 before upgrading to Strimzi 0.32 or newer.
  Please follow the docs for more details.
• The spec.authorization.acls[*].operation field in the KafkaUser resource has been deprecated in favour of the field
  spec.authorization.acls[*].operations which allows to set multiple operations per ACLRule.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

🎉 This PR is included in version 11.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀