Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Helm release strimzi-kafka-operator to v0.45.0 #113

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 4, 2024

This PR contains the following updates:

Package Type Update Change
strimzi-kafka-operator (source) HelmChart minor 0.41.0 -> 0.45.0

Release Notes

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

v0.45.0

Compare Source

  • Add support for Kafka 3.9.0 and 3.8.1.
    Remove support for Kafka 3.7.0 and 3.7.1
  • Ability to move data between JBOD disks using Cruise Control.
  • Allow using custom certificates for communication with container registry in Kafka Connect Build with Kaniko
  • Only roll pods once for ClientsCa cert renewal.
    This change also means the restart reason ClientCaCertKeyReplaced is removed and either CaCertRenewed or CaCertHasOldGeneration will be used.
  • Allow rolling update for new cluster CA trust (during Cluster CA key replacement) to continue where it left off before interruption without rolling all pods again.
  • Update HTTP bridge to 0.31.1
  • Add support for mounting CSI volumes using the template sections
Major changes, deprecations and removals

v0.44.0

Compare Source

  • 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 as the project was discontinued and archived.

v0.43.0

Compare Source

  • Add support for Apache Kafka 3.8.0.
    Remove support for Apache Kafka 3.6.0, 3.6.1, and 3.6.2.
  • Added alerts for Connectors/Tasks in failed state.
  • Support for specifying additional volumes and volume mounts in Strimzi custom resources
  • Strimzi Drain Cleaner updated to 1.2.0 (included in the Strimzi installation files)
  • Additional OAuth configuration options have been added for 'oauth' authentication on the listener and the client.
    On the listener serverBearerTokenLocation and userNamePrefix have been added.
    On the client accessTokenLocation, clientAssertion, clientAssertionLocation, clientAssertionType, and saslExtensions have been added.
  • Add support for custom Cruise Control API users
  • Update HTTP bridge to latest 0.30.0 release
  • Unregistration of KRaft nodes after scale-down
  • Update Kafka Exporter to 1.8.0 and update the Grafana dashboard to work with it
Changes, deprecations and removals
  • The storage overrides for configuring per-broker storage class are deprecated and will be removed in the future.
    If you are using the storage overrides, you should migrate to KafkaNodePool resources and use multiple node pools with a different storage class each.
  • Strimzi 0.43.0 (and any of its patch releases) is the last Strimzi version with support for Kubernetes 1.23 and 1.24.
    From Strimzi 0.44.0 on, we will support only Kubernetes 1.25 and newer.

v0.42.0

Compare Source

  • Add support for Kafka 3.7.1
  • The UseKRaft feature gate moves to GA stage and is permanently enabled without the possibility to disable it.
    To use KRaft (ZooKeeper-less Apache Kafka), you still need to use the strimzi.io/kraft: enabled annotation on the Kafka custom resources or migrate from an existing ZooKeeper-based cluster.
  • Update the base image used by Strimzi containers from UBI8 to UBI9
  • Add support for filename patterns when configuring trusted certificates
  • Enhance KafkaBridge resource with consumer inactivity timeout and HTTP consumer/producer enablement.
  • Add support for feature gates to User and Topic Operators
  • Add support for setting publishNotReadyAddresses on services for listener types other than internal.
  • Update HTTP bridge to latest 0.29.0 release
  • Uncommented and enabled (by default) KRaft-related metrics in the kafka-metrics.yaml example file.
  • Added support for configuring the quotas plugin with type strimzi or kafka in the Kafka custom resource.
    The Strimzi Quotas plugin version was updated to 0.3.1.
Changes, deprecations and removals
  • The reconciliationIntervalSeconds configuration for the Topic and User Operators is deprecated, and will be removed when upgrading schemas to v1.
    Use reconciliationIntervalMs converting the value to milliseconds.
  • Usage of Strimzi Quotas plugin version 0.2.0 is not supported, the plugin was updated to 0.3.1 and changed significantly.
    Additionally, from Strimzi 0.42.0 the plugin should be configured in .spec.kafka.quotas section - the configuration of the plugin inside .spec.kafka.config is ignored and should be removed.

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/strimzi-kafka-operator-0.x branch from 9f1c93f to 19eead6 Compare October 6, 2024 15:46
@renovate renovate bot changed the title Update Helm release strimzi-kafka-operator to v0.43.0 Update Helm release strimzi-kafka-operator to v0.44.0 Oct 30, 2024
@renovate renovate bot force-pushed the renovate/strimzi-kafka-operator-0.x branch from 19eead6 to 2ea17cd Compare October 30, 2024 13:55
@renovate renovate bot changed the title Update Helm release strimzi-kafka-operator to v0.44.0 Update Helm release strimzi-kafka-operator to v0.45.0 Dec 17, 2024
@renovate renovate bot force-pushed the renovate/strimzi-kafka-operator-0.x branch from 2ea17cd to d1e1b70 Compare December 17, 2024 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants