The Great Rabbit Hop: A Zero-Downtime Migration from RabbitMQ 3.x to 4.2 on K8s

"Migrating RabbitMQ version 3.9 to 4.2 on Kubernetes is a high-stakes task. Between breaking version gaps and the shift toward Quorum queues, you can't just "hit update." This guide details a strategy using the RabbitMQ Shovel plugin to move data without dropping a single message."

"To get started, download the Minikube binary and move it to your local path to make it globally accessible. Once installed, initialize your cluster with 4GB of memory and 4 CPUs to ensure enough overhead for running multiple RabbitMQ clusters simultaneously."

"To establish full access, we first create the admin identity and assign it the administrator tag to unlock the web dashboard. Finally, we grant "triple-wildcard" permissions (".*") across the default Virtual Host, ensuring the user has the authority to configure, write, and read from any resource during the migration."

Upgrading RabbitMQ from version 3.9 to 4.2 on Kubernetes requires careful planning due to breaking changes and the transition to Quorum queues. This migration strategy employs a blue-green deployment approach using the RabbitMQ Shovel plugin to move data seamlessly. The process begins by setting up a local Kubernetes environment with Minikube configured with 4GB memory and 4 CPUs. The blue cluster runs RabbitMQ 3.9.25, while the green cluster runs version 4.2. Configuration involves creating admin credentials, establishing triple-wildcard permissions on the default Virtual Host, and creating dual tunnels for both the Management UI and AMQP protocol to enable simultaneous browser management and message traffic handling during migration.

Read at Medium