chore(deps): update kubezero-operators-dependencies #52
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/kubezero-operators-kubezero-operators-dependencies"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.23.0
->0.23.2
4.4.3
->4.4.9
0.45.0
->0.46.0
Release Notes
cloudnative-pg/charts (cloudnative-pg)
v0.23.2
Compare Source
CloudNativePG Operator Helm Chart
What's Changed
Full Changelog: https://github.com/cloudnative-pg/charts/compare/cloudnative-pg-v0.23.1...cloudnative-pg-v0.23.2
v0.23.1
Compare Source
CloudNativePG Operator Helm Chart
What's Changed
New Contributors
Full Changelog: https://github.com/cloudnative-pg/charts/compare/cluster-v0.23.0...cloudnative-pg-v0.23.1
bitnami/charts (rabbitmq-cluster-operator)
v4.4.9
v4.4.8
v4.4.7
v4.4.6
v4.4.5
v4.4.4
strimzi/strimzi-kafka-operator (strimzi-kafka-operator)
v0.46.0
Compare Source
Remove support for Kafka 3.8.0 and 3.8.1.
dnsPolicy
anddnsConfig
using thetemplate
sections.ssl.principal.mapping.rules
and custom trusted CAs in Kafka brokers withtype: custom
authenticationThis will make the cluster boot up correctly in IPv6 only environments, where IPv4 preference will break it due to lack of IPv4 addresses.
ContinueReconciliationOnManualRollingUpdateFailure
feature gate moves to GA stage and is permanently enabled without the possibility to disable it.regardingObject
and the Pod in therelated
field.Major changes, deprecations and removals
Please make sure all your clusters are using KRaft before upgrading to Strimzi 0.46.0 or newer!
Please make sure to migrate to MirrorMaker 2 before upgrading to Strimzi 0.46 or newer.
Please use the Apache Kafka EnvVarConfigProvider and Identity Replication Policy instead.
StableConnectIdentities
feature gate is enabled andStrimziPodSets
are used before upgrading.UseStrimziPodSets
feature gate is enabled andStrimziPodSet
resources are used before upgrading.If you are using the storage overrides, you should instead use multiple KafkaNodePool resources with a different storage class each.
For more details about migrating from storage overrides, please follow the documentation.
type: opa
) has been deprecated and will be removed in the future.To use the Open Policy Agent authorizer, you can use the
type: custom
authorization.statefulset.kubernetes.io/pod-name
label from pods and external listeners Kubernetes Services.strimzi.io/pod-name
one instead.secrets
list for mounting additional Kubernetes Secrets intype: custom
authentication was deprecated and will be removed in the future.Please use the template section to configure additional volumes instead.
If you have any custom logging configuration, you might need to update it during the upgrade to Kafka 4.0.
regardingObject
.If you are using
regardingObject
as afield-selector
for listing events you must update the selector to specify the Kafka resource instead..spec.kafka.metrics
, or explicitly add JMXReporter inmetric.reporters
.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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.
62ea16c03e
to8bda0ef19f
chore(deps): update helm release rabbitmq-cluster-operator to v4.4.5to chore(deps): update kubezero-operators-dependencies8bda0ef19f
toe6d173fd0d
e6d173fd0d
to590fd4e8d3
590fd4e8d3
tof7066b5e6f
f7066b5e6f
to23fb117e7f
23fb117e7f
to5788cd607e
Checkout
From your project repository, check out a new branch and test the changes.