Update module github.com/rabbitmq/cluster-operator to v2 #492
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:
v1.14.0
->v2.10.0
Release Notes
rabbitmq/cluster-operator (github.com/rabbitmq/cluster-operator)
v2.10.0
Compare 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
patchesStrategicMerge
with v1beta1patches
. by @MirahImage in https://github.com/rabbitmq/cluster-operator/pull/1658New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.9.0...v2.10.0
v2.9.0
Compare 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.8.0...v2.9.0
v2.8.0
Compare Source
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.7.0...v2.8.0
v2.7.0
Compare Source
What's Changed
Full Changelog: rabbitmq/cluster-operator@v2.6.0...v2.7.0
v2.6.0
Compare Source
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.5.0...v2.6.0
v2.5.0
Compare Source
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.4.0...v2.5.0
v2.4.0
Compare Source
What's Changed
IMPORTANT: When upgrading to RabbitMQ 3.12 from older versions, please make sure:
rabbitmqctl list_feature_flags
,rabbitmqctl enable_feature_flag all
)Please consult the documentation for more information about upgrading.
Full Changelog: rabbitmq/cluster-operator@v2.3.0...v2.4.0
v2.3.0
Compare Source
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.2.0...v2.3.0
v2.2.0
Compare Source
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.1.0...v2.2.0
v2.1.0
Compare 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.
Multi-arch support
The RabbitMQ cluster-operator now supports both AMD64 and ARM64 architectures out of the box. The image used in the release manifest is a multi-architecture OCI, which is automatically resolved by your container runtime to the underlying image relevant to your architecture.
What's Changed
New Contributors
Full Changelog: rabbitmq/cluster-operator@v2.0.0...v2.1.0
v2.0.0
: 2.0.0Compare Source
Breaking Changes⚠️
This version requires RabbitMQ
3.9.9
upwards. Please ensure all existing RabbitMQ clusters are3.9.9
upwards before upgrading else those RabbitMQ clusters will fail to start after cluster-operator upgrade.If you cannot upgrade some of your existing RabbitMQ clusters to
3.9.9
or newer, pause reconciliation before upgrading the cluster-operator.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@v1.14.0...v2.0.0
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, 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 Renovate Bot.