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 Deploy 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 Deploy Helm chart will deploy the RabbitMQ HA instances, by default. However, if you plan on using your own RabbitMQ instance with Deploy, then you need to follow the steps given below.

Edit the following in the values.yaml file:

  • Change 'rabbitmq-ha.install' to 'false'
  • UseExistingMQ.Enabled: true
  • UseExistingMQ.XLD_TASK_QUEUE_USERNAME: Username for xl-deploy task queue
  • UseExistingMQ.XLD_TASK_QUEUE_PASSWORD: Password for xl-deploy task queue
  • UseExistingMQ.XLD_TASK_QUEUE_URL: amqp://<rabbitmq-service-name>.<namsepace>.svc.cluster.local:5672
  • UseExistingMQ.XLD_TASK_QUEUE_DRIVER_CLASS_NAME: com.rabbitmq.jms.admin.RMQConnectionFactory

The rabbitmq-service-name is obtained by executing command

oc get service

get service only RabbitMQ info

Enabled: true
#If you want to use an existing Message Queue, change
'rabbitmq-ha.install' to 'false'.
#Set 'UseExistingMQ.Enabled' to 'true'.Uncomment the following:
lines and provide the values.
XLD_TASK_QUEUE_DRIVER_CLASS_NAME: com.rabbitmq.jms.admin.RMQConnectionFactory


  • Currently we only support the amqp protocol for messaging queue.
  • If you have the rabbitmq instance running outside the cluster. Configure the parameters mentioned above to match your setup accordingly.
  • For OpenShift, one may either define the scc for Rabbitmq accordingly. However, we have used the default scc anyuid

Next Step