chore(deps): update dependency rabbitmq-cluster-operator to v2.22.1#685
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency rabbitmq-cluster-operator to v2.22.1#685renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
779d0aa to
368dbeb
Compare
368dbeb to
5c5cf7c
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.21.1→2.22.1v2.21.1→v2.22.1Release Notes
rabbitmq/cluster-operator (rabbitmq-cluster-operator)
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
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.