Update Helm release strimzi-kafka-operator to v1.2.0
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.1.0 → 1.2.0 |
Release Notes
strimzi/strimzi-kafka-operator (strimzi-kafka-operator)
v1.2.0
- Add support for Apache Kafka 4.3.1
- Support templated (per-pod) additional volumes for Kafka, Kafka Connect and Kafka MirrorMaker 2 operands
- Stop auto-mounting Service Account tokens into Pods and mount them through a volume instead
- The
ServerSideApplyPhase1feature gate moves to GA stage and is permanently enabled without the possibility to disable it. - Support for configuring Maven mirrors for Kafka Connect Build
- Connectors that request the
stoppedorpausedstate viaspec.stateare now created directly in that state instead of being started first and then stopped or paused. - Added support for broker cordoning KIP-1066 during auto-rebalancing on scale down for Kafka 4.3+.
- Removed deprecated resource state metrics - the KSM (kube-state-metrics) should be used instead.
- Update Strimzi metrics-reporter to 0.4.0
- Update strimzi-kafka-oauth to 0.18.0
Major changes, deprecations, and removals
- The Cluster, Topic, and User Operator YAML installation files and the Cluster Operator Helm Chart now use the default container security context that matches the Restricted Kubernetes Pod Security Standard.
If needed, you can override the default security context by updating thesecurityContextproperty in the YAML installation files or use thesecurityContextproperty in the Cluster Operator Helm Chart values.
