Skip to main content
Version: Deploy 24.1

Manual upgrade RabbitMQ

RabbitMQ during operator2operator upgrade or helm2operator upgrade to version 23.3 of operator will not upgrade automatically to the latest RabbitMQ server version. It will upgrade maximally to the RabbitMQ server 3.10.25 (in 23.1 we are using the server version 3.9.8-debian-10-r6). The version that is installed with operator 23.3. Is RabbitMQ server 3.12.3-debian-11-r1. So we need to manually upgrade to that version, because we need to enable RabbitMQ feature in each version, see following links for more details:

Steps to upgrade from RabbitMQ server 3.10.25 to 3.12.3​

  • If the current version is 3.10.x, upgrade to 3.11.23

Scale down the Deploy pods:

kubectl patch digitalaideployments.deploy.digital.ai dai-xld -n digitalai \
  --type=merge \
  --patch '{"spec": {"replicaCount": 0}}'

Enable all available feature flags:

kubectl exec -n digitalai dai-xld-rabbitmq-0 -c rabbitmq -- \
  rabbitmqctl list_feature_flags

kubectl exec -n digitalai dai-xld-rabbitmq-0 -c rabbitmq -- \
  rabbitmqctl enable_feature_flag all

Patch the RabbitMQ image version (explicit or default):

Option 1: Set a specific version Explicitly set the RabbitMQ image tag to a known version.

kubectl patch -n digitalai Digitalaideploys dai-xlr \
  --type=merge --patch '{"spec": {"rabbitmq": {"image": {"tag": "3.11.23"}}}}'
  • if the current version is 3.11.x, upgrade to 3.12.3

Option 2: Remove the image tag to use the operator’s default (latest supported version) To move to the default version provided by the current operator, clear the image tag field:

kubectl patch -n digitalai Digitalaideploys dai-xlr \
  --type=merge --patch '{"spec": {"rabbitmq": {"image": null}}}'

Restore the Deploy pods to the replica count used before the upgrade (e.g., 1):

kubectl patch digitalaideployments.deploy.digital.ai dai-xld -n digitalai \
  --type=merge \
  --patch '{"spec": {"replicaCount": 1}}'

Adjust the value 1 to match the original replica count used in your environment.