Skip to main content
Version: Deploy 23.3

Using an Existing RabbitMQ Message Queue

If you plan to use an existing message queue — one that is not created by default by the Operator-based installer — you must configure the relevant MQ parameters in the daideploy_cr.yaml file.

If you have already run Deploy instance check Migrate to Existing Message Queue

Note: Skip this section if you do not want to use your own message queue instance. The Digital.ai Deploy Operator creates a RabbitMQ instance by default. This procedure is for those who want to use an existing message queue server with Digital.ai Deploy.

Configure an External Message Queue During installation​

Once you have your external message queue up and running, set the following parameters in the daideploy_cr.yaml file. They are set by answering to the question during installation: Edit RabbitMQ external setup:.

  • external.mq.url — the existing message queue broker URL
  • external.mq.queueName — Message queue name for xl-deploy
  • external.mq.username — Message queue user for xl-deploy
  • external.mq.password — Message queue password for xl-deploy
  • external.mq.driverClassName — Message queue driver class name

Here's an example.

    url: "amqp://rabbitmq-test1.default.svc.cluster.local:5672"
    queueName: ""
    username: "user"
    password: "password"
    driverClassName: "com.rabbitmq.jms.admin.RMQConnectionFactory"

Note: If you have your message queue instance running outside the cluster, configure the parameters above to match your setup.