Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update module github.com/rabbitmq/cluster-operator to v2 #492

Conversation

openstack-k8s-ci-robot
Copy link

This PR contains the following updates:

Package Type Update Change
github.com/rabbitmq/cluster-operator require major v1.14.0 -> v2.10.0

Release Notes

rabbitmq/cluster-operator (github.com/rabbitmq/cluster-operator)

v2.10.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.9.0...v2.10.0

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

  • use RabbitMQ 3.12.2 by default

IMPORTANT: When upgrading to RabbitMQ 3.12 from older versions, please make sure:

  1. You currently run 3.11.18 or newer
  2. All feature flags are enabled (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

⚠️ 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.

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

Compare Source

Breaking Changes ⚠️

This version requires RabbitMQ 3.9.9 upwards. Please ensure all existing RabbitMQ clusters are 3.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.

⚠️ 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@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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@openstack-k8s-ci-robot
Copy link
Author

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 12 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.21 -> 1.22.7
github.com/onsi/gomega v1.34.1 -> v1.34.2
k8s.io/api v0.29.9 -> v0.30.1
k8s.io/apimachinery v0.29.9 -> v0.30.3
k8s.io/client-go v0.29.9 -> v0.30.1
sigs.k8s.io/controller-runtime v0.17.6 -> v0.18.5
github.com/google/pprof v0.0.0-20240727154555-813a5fbdbec8 -> v0.0.0-20240827171923-fa2c70bbbfe5
github.com/prometheus/client_golang v1.18.0 -> v1.19.0
github.com/prometheus/common v0.46.0 -> v0.48.0
golang.org/x/sys v0.23.0 -> v0.24.0
k8s.io/apiextensions-apiserver v0.29.2 -> v0.30.1
k8s.io/component-base v0.29.2 -> v0.30.1
k8s.io/klog/v2 v2.120.1 -> v2.130.1

Copy link
Contributor

openshift-ci bot commented Sep 26, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openstack-k8s-ci-robot
Once this PR has been reviewed and has the lgtm label, please assign viroel for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

openshift-ci bot commented Sep 26, 2024

@openstack-k8s-ci-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/precommit-check ca5a52e link true /test precommit-check

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@stuggi stuggi closed this Sep 26, 2024
@openstack-k8s-ci-robot
Copy link
Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@openstack-k8s-ci-robot openstack-k8s-ci-robot deleted the renovate/github.com-rabbitmq-cluster-operator-2.x branch September 26, 2024 10:25
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.

2 participants