strimzi/strimzi-kafka-operator (strimzi-kafka-operator)
### [`v0.44.0`](https://redirect.github.com/strimzi/strimzi-kafka-operator/blob/HEAD/CHANGELOG.md#0440)
[Compare Source](https://redirect.github.com/strimzi/strimzi-kafka-operator/compare/0.43.0...0.44.0)
- Add the "Unmanaged" KafkaTopic status update.
- The `ContinueReconciliationOnManualRollingUpdateFailure` feature gate moves to beta stage and is enabled by default.
If needed, `ContinueReconciliationOnManualRollingUpdateFailure` can be disabled in the feature gates configuration in the Cluster Operator.
- Add support for managing connector offsets via KafkaConnector and KafkaMirrorMaker2 custom resources.
- Add support for templating `host` and `advertisedHost` fields in listener configuration.
- Allow configuration of environment variables based on Config Map or Secret for every container in the container template sections.
- Add support for disabling the generation of PodDisruptionBudget resources by the Cluster Operator.
- Add support for running an automatic rebalancing, via Cruise Control, when the cluster is scaled down or up:
- after a scaling up, the operator triggers an auto-rebalancing for moving some of the existing partitions to the newly added brokers.
- before scaling down, and if the brokers to remove are hosting partitions, the operator triggers an auto-rebalancing to these partitions off the brokers to make them free to be removed.
- Strimzi Access Operator 0.1.0 added to the installation files and examples
##### Changes, deprecations and removals
- **From Strimzi 0.44.0 on, we support only Kubernetes 1.25 and newer.**
Kubernetes 1.23 and 1.24 are not supported anymore.
- When finalizers are enabled (default), the Topic Operator will no longer restore finalizers on unmanaged `KafkaTopic` resources if they are removed, aligning the behavior with paused topics, where finalizers are also not restored.
This change matches user expectations.
- The External Configuration (`.spec.externalConfiguration`) in `KafkaConnect` and `KafkaMirrorMaker2` resources is deprecated and will be removed in the future.
Please use the environment variables, additional volumes and volume mounts in Pod and container templates instead.
- The Strimzi Canary installation files were removed based on the [*Strimzi proposal 086*](https://redirect.github.com/strimzi/proposals/blob/main/086-archive-canary.md) as the project was discontinued and archived.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 contains the following updates:
0.43.0->0.44.0Release Notes
strimzi/strimzi-kafka-operator (strimzi-kafka-operator)
### [`v0.44.0`](https://redirect.github.com/strimzi/strimzi-kafka-operator/blob/HEAD/CHANGELOG.md#0440) [Compare Source](https://redirect.github.com/strimzi/strimzi-kafka-operator/compare/0.43.0...0.44.0) - Add the "Unmanaged" KafkaTopic status update. - The `ContinueReconciliationOnManualRollingUpdateFailure` feature gate moves to beta stage and is enabled by default. If needed, `ContinueReconciliationOnManualRollingUpdateFailure` can be disabled in the feature gates configuration in the Cluster Operator. - Add support for managing connector offsets via KafkaConnector and KafkaMirrorMaker2 custom resources. - Add support for templating `host` and `advertisedHost` fields in listener configuration. - Allow configuration of environment variables based on Config Map or Secret for every container in the container template sections. - Add support for disabling the generation of PodDisruptionBudget resources by the Cluster Operator. - Add support for running an automatic rebalancing, via Cruise Control, when the cluster is scaled down or up: - after a scaling up, the operator triggers an auto-rebalancing for moving some of the existing partitions to the newly added brokers. - before scaling down, and if the brokers to remove are hosting partitions, the operator triggers an auto-rebalancing to these partitions off the brokers to make them free to be removed. - Strimzi Access Operator 0.1.0 added to the installation files and examples ##### Changes, deprecations and removals - **From Strimzi 0.44.0 on, we support only Kubernetes 1.25 and newer.** Kubernetes 1.23 and 1.24 are not supported anymore. - When finalizers are enabled (default), the Topic Operator will no longer restore finalizers on unmanaged `KafkaTopic` resources if they are removed, aligning the behavior with paused topics, where finalizers are also not restored. This change matches user expectations. - The External Configuration (`.spec.externalConfiguration`) in `KafkaConnect` and `KafkaMirrorMaker2` resources is deprecated and will be removed in the future. Please use the environment variables, additional volumes and volume mounts in Pod and container templates instead. - The Strimzi Canary installation files were removed based on the [*Strimzi proposal 086*](https://redirect.github.com/strimzi/proposals/blob/main/086-archive-canary.md) as the project was discontinued and archived.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.