Skip to content

chore(deps): update dependency rabbitmq-cluster-operator to v2.22.1#685

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rabbitmq-cluster-operator-2.x
Open

chore(deps): update dependency rabbitmq-cluster-operator to v2.22.1#685
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rabbitmq-cluster-operator-2.x

Conversation

@renovate

@renovate renovate Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
rabbitmq-cluster-operator minor 2.21.12.22.1
rabbitmq/cluster-operator minor v2.21.1v2.22.1

Release Notes

rabbitmq/cluster-operator (rabbitmq-cluster-operator)

v2.22.1

Compare Source

⚠️ Upgrading the cluster-operator to this version will update RabbitMQ clusters (i.e. will cause rolling update of the underlying StatefulSets).
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

  • Fix metrics cert secret collision by giving secret a unique name. by @​MirahImage in #​2189
  • Wait for OLM webhook service endpoints before creating RabbitmqCluster in OLM test by @​Zerpet in #​2191

Full Changelog: rabbitmq/cluster-operator@v2.22.0...v2.22.1

v2.22.0

Compare Source

⚠️⚠️⚠️ POTENTIAL BREAKING CHANGE ⚠️⚠️⚠️

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.


⚠️ Upgrading the cluster-operator to this version will update RabbitMQ clusters (i.e. will cause rolling update of the underlying StatefulSets).
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


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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/rabbitmq-cluster-operator-2.x branch from 779d0aa to 368dbeb Compare July 5, 2026 14:50
@renovate renovate Bot force-pushed the renovate/rabbitmq-cluster-operator-2.x branch from 368dbeb to 5c5cf7c Compare July 6, 2026 13:46
@renovate renovate Bot changed the title chore(deps): update dependency rabbitmq-cluster-operator to v2.22.0 chore(deps): update dependency rabbitmq-cluster-operator to v2.22.1 Jul 6, 2026
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