Skip to main content
Version: Early Access

Using an External Message Queue

This topic illustrates how to use an external message queue, instead of the RabbitMQ that is provided with the operator itself.

This document describes how to change configuration on the existing Deploy installation. If you are doing initial installation, check the document Using an Existing Message Queue

Steps to Configure an External Message Queue after Installation​

  1. Prepare the external message queue configuration.
spec:
  external:
    mq:
      enabled: true
      url: "amqp://rabbitmq-test1.default.svc.cluster.local:5672"
      queueName: ""
      username: "user"
      password: "password"
  rabbitmq:
    install: false
  1. Update the message queue configuration in Release.
kubectl patch -n digitalai digitalaireleases.xlr.digital.ai dai-xlr \
  --type=merge --patch-file external-mq-patch.yaml
  1. The Release pods are automatically restarted.
  2. The CR yaml file will now have a new external.mq section.
kubectl get Digitalaireleases dai-xlr -o yaml -n digitalai
  1. The restarted pod process will now use the new configuration.
kubectl exec -it sts/dai-xlr-digitalai-release -n digitalai \
  -- cat /opt/xebialabs/xl-release-server/conf/xl-release.conf