Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 28, 2025

This PR contains the following updates:

Package Update Change
rabbitmq/cluster-operator minor 2.16.1 -> 2.18.0

Release Notes

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

v2.18.0

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

New Contributors

Full Changelog: rabbitmq/cluster-operator@v2.17.2...v2.18.0

v2.17.2

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

Full Changelog: rabbitmq/cluster-operator@v2.17.1...v2.17.2

v2.17.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

Full Changelog: rabbitmq/cluster-operator@v2.17.0...v2.17.1

v2.17.0

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.

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: 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.


  • 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 b88b31a to c80255f Compare December 1, 2025 06:18
@renovate renovate bot changed the title chore(deps): update dependency rabbitmq/cluster-operator to v2.17.2 chore(deps): update dependency rabbitmq/cluster-operator to v2.18.0 Dec 10, 2025
@renovate renovate bot force-pushed the renovate/rabbitmq-cluster-operator-2.x branch from c80255f to af64795 Compare December 10, 2025 13:27
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.

1 participant