fix(rabbitmq): do not set old ha-mode policies and set the mem request equal to the limit#1797
Merged
Conversation
Our ha-mode policy is not compatible with newer versions of RabbitMQ and results in the rabbitmq-operator displaying errors. Since we are working to upgrade just remove it now to avoid upgrade issues.
The rabbitmq-operator documentation says that the request and the limit should be set to the same value and the operator warns when it is not.
cardoe
changed the title
nicholaskuechler
approved these changes
Mar 11, 2026
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
2 participants
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.
To prepare for the upgrade to RabbitMQ 4.x, we should drop the unsupported ha-mode policy setting which conflicts for queue creation. The rabbitmq-operator wants the mem request and limit to be equal to each other so set that by default.