chore(deps): update dependency rabbitmq/cluster-operator to v2.22.3#1455
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency rabbitmq/cluster-operator to v2.22.3#1455renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
December 1, 2025 06:18
b88b31a to
c80255f
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
December 10, 2025 13:27
c80255f to
af64795
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
January 12, 2026 11:26
af64795 to
9f17bdb
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
February 2, 2026 15:47
9f17bdb to
65b57c4
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
2 times, most recently
from
February 12, 2026 12:07
d11b8e6 to
8f330b3
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
March 11, 2026 13:29
8f330b3 to
a7fb76f
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
March 25, 2026 17:29
a7fb76f to
7da59ce
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
April 16, 2026 12:46
7da59ce to
0602a64
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
May 13, 2026 14:36
0602a64 to
ae3fbd4
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
May 14, 2026 15:29
ae3fbd4 to
40e6e1d
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
June 9, 2026 17:11
40e6e1d to
36faeec
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
July 1, 2026 19:11
36faeec to
7af835f
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
July 6, 2026 08:02
7af835f to
ee8fbe4
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
July 14, 2026 11:52
ee8fbe4 to
bda6e1f
Compare
renovate
Bot
force-pushed
the
renovate/rabbitmq-cluster-operator-2.x
branch
from
July 17, 2026 14:52
bda6e1f to
a18a421
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
2.16.1→2.22.3Release Notes
rabbitmq/cluster-operator (rabbitmq/cluster-operator)
v2.22.3Compare Source
v2.22.2Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.22.1...v2.22.2
v2.22.1Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.22.0...v2.22.1
v2.22.0Compare Source
This version of the operator introduces a new startup probe for RabbitMQ. It moves from an exec probe to an HTTP probe. The HTTP probe is available in RabbitMQ 4.2.4+ and 4.3.0+. Earlier versions of RabbitMQ do not have the HTTP endpoint required for this probe. The recommendation is to upgrade to latest 4.3 or 4.2 patch.
If you can't upgrade to 4.2 or 4.3 you can use the annotation
rabbitmq.com/legacy-startup-probe: "true"to fallback to previous behaviour. NOTE that you are running an unsupported community version if you must use this annotation.If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.21.1...v2.22.0
v2.21.1Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.21.0...v2.21.1
v2.21.0Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.20.1...v2.21.0
v2.20.1Compare Source
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.20.0...v2.20.1
v2.20.0Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.19.2...v2.20.0
v2.19.2Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.19.1...v2.19.2
v2.19.1Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.19.0...v2.19.1
v2.19.0Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.18.0...v2.19.0
v2.18.0Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.17.2...v2.18.0
v2.17.2Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.17.1...v2.17.2
v2.17.1Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.17.0...v2.17.1
v2.17.0Compare Source
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.
Potential breaking changes
For Openshift users, the enhanced security context might cause downtime if the security context is not overridden, as documented in our updated example or our website docs.
Enhanced Security Context
The cluster operator now has a security context, and sets an enhanced security context for RabbitMQ clusters. For users on OpenShift and other cases where the security context is overridden, please make use of our updated example.
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.16.1...v2.17.0
Configuration
📅 Schedule: (UTC)
🚦 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.