RabbitMQ: explain how to safely avoid an OrderedReady-induced deployment deadlock
#25916
Conversation
This file contains 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
Explain the problem and a widely used solution instead of recommending force booting nodes. These practices are generally used by existing RabbitMQ K8S Cluster Operators but this PR intentionally does not recommend any of them. Signed-off-by: Michael Klishin <[email protected]> Signed-off-by: Michael Klishin <[email protected]> Signed-off-by: Michael Klishin <[email protected]>
This was referenced May 15, 2024
Closed
carrodher
reviewed
May 15, 2024
Co-authored-by: Carlos Rodríguez Hernández <[email protected]> Signed-off-by: Michael Klishin <[email protected]>
|
I will have to submit another PR because of https://github.com/bitnami/charts/pull/25916/checks?check_run_id=25008225640. My default GitHub account email is not what DCO expects and even if I squash and push, that workflow somehow does not detect the changes. |
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.
Explain the problem and a widely used solution
instead of recommending force booting nodes.
These practices are generally used by existing
RabbitMQ K8S Cluster Operators but this PR
intentionally does not recommend any of them.
References #25698 and #16081.