Using your own MQ

If you are planning to use an existing MQ, you will need to configure the environment variables, in the values.yaml file.

See this documentation link for a basic understanding of environment variables used in the Release helm chart.

Using an existing or external messaging queue

Note: Skip this section if you do not want to use your own RabbitMQ HA instance. The Release Helm chart will deploy the RabbitMQ HA instances, by default. However, if you plan on using your own RabbitMQ instance with Release, then you need to follow the steps given below.

Edit the following in the values.yaml file:

  • Change 'rabbitmq.install' to 'false'
  • UseExistingMQ.Enabled: true
  • UseExistingMQ.XLR_TASK_QUEUE_USERNAME: Username for xl-task queue
  • UseExistingMQ.XLR_TASK_QUEUE_PASSWORD: Password for xl-task queue
  • UseExistingMQ.XLR_TASK_QUEUE_NAME: Queue Name for xl-release
  • UseExistingMQ.XLR_TASK_QUEUE_URL: amqp://<rabbitmq-service-name>.<namsepace>.svc.cluster.local:5672

The rabbitmq-service-name is obtained by executing command

kubectl get service

get service only RabbitMQ info

Enabled: true
#If you want to use an existing Message Queue, change
'rabbitmq.install' to 'false'.
#Set 'UseExistingMQ.Enabled' to 'true'.Uncomment the following:
lines and provide the values.
XLR_TASK_QUEUE_NAME: xlr-task-queue

Note: Currently we only support the amqp protocol for messaging queue.

Note: If you have the rabbitmq instance running outside the cluster. Configure the parameters mentioned above to match your setup accordingly.

Note: RabbitMQ username and passwords are now stored in kubernetes secrets.

Next Step