Shovel can move messages between move messages reliably and continually (typically between queues). In this example, we will declare a dynamic Shovel that moves messages from a classic queue to a quorum queue in the same RabbitmqCluster. The example can be used when you want to migrate from classic or mirrored queues to quorum queues.
Before creating any topology objects with Messaging Topology Operator, please deploy a RabbitmqCluster named example-rabbit, or any name you see fit. You will need to enable the rabbitmq_shovel plugin and here is an example from the cluster operator repo about enabling additional plugins.
After the RabbitMQ cluster is successfully created, you need to get username and password of the default user for this RabbitMQ cluster:
kubectl get secret example-rabbit-default-user -o jsonpath='{.data.username}' | base64 --decode
kubectl get secret example-rabbit-user -o jsonpath='{.data.password}' | base64 --decodeSave the username and password, because we need both later to construct the source and destination URI.
This example includes (please create in order):
- two vhosts: 'source' and 'destination'
- a Kubernetes secret 'shovel-secret' containing the shovel source and destination URIs
- a classic queue 'source-queue' in vhost 'source' vhost
- a quorum queue 'destination-queue' in vhost 'destination'
- shovel 'shovel-example' between queue 'source-queue' and queue 'destination-queue'
After all topology objects are created, messages in 'source queue' will be moved into 'destination-queue'.