Update Helm release strimzi-kafka-operator to v0.41.0 - autoclosed #416
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.40.0
->0.41.0
Release Notes
strimzi/strimzi-kafka-operator (strimzi-kafka-operator)
v0.41.0
Compare Source
Strimzi Operators
dashboard to include certificate expiration per cluster.(Note: JBOD support in KRaft mode is considered early-access in Apache Kafka 3.7.x)
KafkaNodePools
feature gate moves to GA stage and is permanently enabled without the possibility to disable it.To use the Kafka Node Pool resources, you still need to use the
strimzi.io/node-pools: enabled
annotation on theKafka
custom resources.externalIPs
field in node port type services.UnidirectionalTopicOperator
feature gate moves to GA stage and is permanently enabled without the possibility to disable it.If the topics whose names start with
strimzi-store-topic
andstrimzi-topic-operator
still exist, you can delete them.AWS_MSK_IAM
)strimzi.io/manual-rolling-update
annotation (when theContinueReconciliationOnManualRollingUpdateFailure
feature gate is enabled).Changes, deprecations and removals
tlsSidecar
configuration for the Entity Operator is now deprecated and will be ignored.zookeeperSessionTimeoutSeconds
andtopicMetadataMaxAttempts
configurations for the Entity Topic Operator have been removed and will be ignored.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 has been generated by Mend Renovate. View repository job log here.