title: How to scale RabbitMQ across multiple Kubernetes Clusters
body: <p>I have an application running in a Kubernetes cluster Azure AKS which is made up of a website running in one deployment, background worker processes running as scheduled tasks in Kubernetes, RabbitMQ running as another deployment and a SQL Azure DB which is not part of the Kubernetes.</p>
  
  <p>I would like to deploy achieve load balancing and failover by deploying another kubernetes cluster in another region and placing a Traffic Manager DNS Load Balancer in front of the web site.</p>
  
  <p>The problem that I see is that if the two rabbit instances are in separate kubernetes clusters then items queued in one will not be available in the other. </p>
  
  <p>Is there a way to cluster the rabbitmq instances running in each kubernetes cluster or something besides clustering?
  Or is there a common design pattern that might avoid problems from having seperate queues?</p>
  
  <p>I should also note that currently there is only one node running RabbitMq in the current kuberntes cluster but as part of this upgrade it seems like a good idea to run multiple nodes in each cluster which I think the current Helm charts support.</p>