Upgrade RMQ to 3.13 #108
Open
Upgrade RMQ to 3.13 #108
Conversation
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
…elay before enabling feature flags
…r RabbitMQ upgrade
Contributor
Author
|
RMQ 3.13.7 is running on node W087 as a test case |
… and add enable_rmq_ft_flags to handle feature flag enabling with retry logic.
…nfigurations during updates.
…ion is updated before proceeding with RabbitMQ upgrades.
…gement and ensuring version checks are performed before applying updates.
…d minor versions are reached before proceeding with updates.
…ocess in update-stack.sh
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 pull request introduces an automated RabbitMQ upgrade process to the
kubernetes/update-stack.shscript, along with updates to the RabbitMQ configuration and Kubernetes manifest. The main focus is on safely upgrading RabbitMQ through supported intermediate versions, ensuring data backup, feature flag management, and comprehensive health checks and logging. Additionally, new queues, exchanges, and bindings are added to the RabbitMQ configuration, and the target RabbitMQ version is bumped in the deployment manifest.RabbitMQ Upgrade Automation and Safety
update_rabbitmq_version,determine_rabbitmq_upgrade_path, andupgrade_rabbitmq_to_versionfunctions to automate RabbitMQ upgrades, handling intermediate versions, data backup, feature flag enabling, health checks, and logging. These functions ensure upgrades follow official supported paths and prevent downgrades. (kubernetes/update-stack.sh)kubernetes/update-stack.sh)3.8.11-management-alpineto3.13.7-management-alpine, aligning with the upgrade logic. (kubernetes/wes-rabbitmq.yaml)RabbitMQ Configuration Enhancements
ansible,to-validator), exchanges (to-validator), and bindings for improved message routing and integration with validator and ansible components. (kubernetes/update-stack.sh) [1] [2] [3]kubernetes/update-stack.sh)