Update Helm release strimzi-kafka-operator to v0.45.0 #113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.41.0
->0.45.0
Release Notes
strimzi/strimzi-kafka-operator (strimzi-kafka-operator)
v0.45.0
Compare Source
Remove support for Kafka 3.7.0 and 3.7.1
This change also means the restart reason ClientCaCertKeyReplaced is removed and either CaCertRenewed or CaCertHasOldGeneration will be used.
template
sectionsMajor changes, deprecations and removals
Please make sure to migrate to KRaft and MirrorMaker 2 before upgrading to Strimzi 0.46 or newer.
Please use the Apache Kafka EnvVarConfigProvider and Identity Replication Policy instead.
v0.44.0
Compare Source
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.host
andadvertisedHost
fields in listener configuration.Changes, deprecations and removals
Kubernetes 1.23 and 1.24 are not supported anymore.
KafkaTopic
resources if they are removed, aligning the behavior with paused topics, where finalizers are also not restored.This change matches user expectations.
.spec.externalConfiguration
) inKafkaConnect
andKafkaMirrorMaker2
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.
v0.43.0
Compare Source
Remove support for Apache Kafka 3.6.0, 3.6.1, and 3.6.2.
On the listener
serverBearerTokenLocation
anduserNamePrefix
have been added.On the client
accessTokenLocation
,clientAssertion
,clientAssertionLocation
,clientAssertionType
, andsaslExtensions
have been added.Changes, deprecations and removals
If you are using the storage overrides, you should migrate to KafkaNodePool resources and use multiple node pools with a different storage class each.
From Strimzi 0.44.0 on, we will support only Kubernetes 1.25 and newer.
v0.42.0
Compare Source
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 theKafka
custom resources or migrate from an existing ZooKeeper-based cluster.KafkaBridge
resource with consumer inactivity timeout and HTTP consumer/producer enablement.publishNotReadyAddresses
on services for listener types other than internal.kafka-metrics.yaml
example file.strimzi
orkafka
in theKafka
custom resource.The Strimzi Quotas plugin version was updated to 0.3.1.
Changes, deprecations and removals
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.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.
This PR was generated by Mend Renovate. View the repository job log.