Install latest version (3.10) of RabbitMQ

[padowla]

Does someone know a way to force the latest cluster operator (1.12.1) to install the image 3.10 for the broker server?
Referring to the official documentation of cluster operator:

The operator deploys RabbitMQ 3.10.1 by default, and supports versions from 3.8.8 upwards. The operator requires Kubernetes 1.19 or newer.

Although the operator is at the new version:

Name:         rabbitmq-cluster-operator-587f65b9c4-ttm44
Namespace:    rabbitmq-system
Priority:     0
Node:         aks-agentpool-26816451-vmss000000/10.224.0.4
Start Time:   Thu, 12 May 2022 10:05:58 +0200
Labels:       app.kubernetes.io/component=rabbitmq-operator
              app.kubernetes.io/name=rabbitmq-cluster-operator
              app.kubernetes.io/part-of=rabbitmq
              pod-template-hash=587f65b9c4
Annotations:  <none>
Status:       Running
IP:           10.244.2.4
IPs:
  IP:           10.244.2.4
Controlled By:  ReplicaSet/rabbitmq-cluster-operator-587f65b9c4
Containers:
  operator:
    Container ID:  containerd://f28e54f7ce449bc90a590507075ec3c205279e36deafdd0c96d3fa4db29f8ce6
    Image:         rabbitmqoperator/cluster-operator:1.12.1
    Image ID:      docker.io/rabbitmqoperator/cluster-operator@sha256:34b7ff374582b59f9738d2e538b4e22785ccdd68c58c190bbf9216269ac72756
    Port:          9782/TCP
    Host Port:     0/TCP
    Command:
      /manager
    State:          Running
      Started:      Thu, 12 May 2022 10:05:59 +0200
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     200m
      memory:  500Mi
    Requests:
      cpu:     200m
      memory:  500Mi
    Environment:
      OPERATOR_NAMESPACE:  rabbitmq-system (v1:metadata.namespace)
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-4m4wg (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  kube-api-access-4m4wg:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Guaranteed
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  17m   default-scheduler  Successfully assigned rabbitmq-system/rabbitmq-cluster-operator-587f65b9c4-ttm44 to aks-agentpool-26816451-vmss000000
  Normal  Pulled     17m   kubelet            Container image "rabbitmqoperator/cluster-operator:1.12.1" already present on machine
  Normal  Created    17m   kubelet            Created container operator
  Normal  Started    17m   kubelet            Started container operator

The broker is installed with the old version (3.9.13):

Name:         broker-server-0
Namespace:    broker
Priority:     0
Node:         aks-agentpool-26816451-vmss000002/10.224.0.6
Start Time:   Thu, 12 May 2022 10:20:32 +0200
Labels:       app.kubernetes.io/component=rabbitmq
              app.kubernetes.io/name=broker
              app.kubernetes.io/part-of=rabbitmq
              controller-revision-hash=broker-server-d6956c7f7
              statefulset.kubernetes.io/pod-name=broker-server-0
Annotations:  prometheus.io/port: 15691
              prometheus.io/scrape: true
Status:       Running
IP:           10.244.1.7
IPs:
  IP:           10.244.1.7
Controlled By:  StatefulSet/broker-server
Init Containers:
  setup-container:
    Container ID:  containerd://567d980f851575c9204ff6b5b38b3fe0a13b5a060a12054f13388ca416ca77ef
    Image:         rabbitmq:3.9.13-management
    Image ID:      docker.io/library/rabbitmq@sha256:981f32e8962311fb94e1cc11b868b2790f23a49a003310c6b0fdfcd4b8f6fbe6
    Port:          <none>
    Host Port:     <none>
    Command:
      sh
      -c
      cp /tmp/erlang-cookie-secret/.erlang.cookie /var/lib/rabbitmq/.erlang.cookie && chmod 600 /var/lib/rabbitmq/.erlang.cookie ; cp /tmp/rabbitmq-plugins/enabled_plugins /operator/enabled_plugins ; echo '[default[]' > /var/lib/rabbitmq/.rabbitmqadmin.conf && sed -e 's/default_user/username/' -e 's/default_pass/password/' /tmp/default_user.conf >> /var/lib/rabbitmq/.rabbitmqadmin.conf && chmod 600 /var/lib/rabbitmq/.rabbitmqadmin.conf
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Thu, 12 May 2022 10:20:47 +0200
      Finished:     Thu, 12 May 2022 10:20:47 +0200
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     100m
      memory:  500Mi
    Requests:
      cpu:        100m
      memory:     500Mi
    Environment:  <none>
    Mounts:
      /operator from rabbitmq-plugins (rw)
      /tmp/default_user.conf from rabbitmq-confd (rw,path="default_user.conf")
      /tmp/erlang-cookie-secret/ from erlang-cookie-secret (rw)
      /tmp/rabbitmq-plugins/ from plugins-conf (rw)
      /var/lib/rabbitmq/ from rabbitmq-erlang-cookie (rw)
      /var/lib/rabbitmq/mnesia/ from persistence (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-68pdx (ro)
Containers:
  rabbitmq:
    Container ID:   containerd://61e2ea574422e647877c382a1111e0b53bfaf60e3c88634ca7b01da51c18d7ac
    Image:          rabbitmq:3.9.13-management
    Image ID:       docker.io/library/rabbitmq@sha256:981f32e8962311fb94e1cc11b868b2790f23a49a003310c6b0fdfcd4b8f6fbe6
    Ports:          4369/TCP, 5671/TCP, 15671/TCP, 15691/TCP, 8883/TCP
    Host Ports:     0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP
    State:          Running
      Started:      Thu, 12 May 2022 10:20:48 +0200
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  2G
    Requests:
      cpu:      1
      memory:   2G
    Readiness:  tcp-socket :amqps delay=10s timeout=5s period=10s #success=1 #failure=3
    Environment:
      MY_POD_NAME:                    broker-server-0 (v1:metadata.name)
      MY_POD_NAMESPACE:               broker (v1:metadata.namespace)
      K8S_SERVICE_NAME:               broker-nodes
      RABBITMQ_ENABLED_PLUGINS_FILE:  /operator/enabled_plugins
      RABBITMQ_USE_LONGNAME:          true
      RABBITMQ_NODENAME:              rabbit@$(MY_POD_NAME).$(K8S_SERVICE_NAME).$(MY_POD_NAMESPACE)
      K8S_HOSTNAME_SUFFIX:            .$(K8S_SERVICE_NAME).$(MY_POD_NAMESPACE)
    Mounts:
      /etc/pod-info/ from pod-info (rw)
      /etc/rabbitmq-tls/ from rabbitmq-tls (ro)
      /etc/rabbitmq/conf.d/10-operatorDefaults.conf from rabbitmq-confd (rw,path="operatorDefaults.conf")
      /etc/rabbitmq/conf.d/11-default_user.conf from rabbitmq-confd (rw,path="default_user.conf")
      /etc/rabbitmq/conf.d/90-userDefinedConfiguration.conf from rabbitmq-confd (rw,path="userDefinedConfiguration.conf")
      /etc/ssl/certs/snam-ca.pem from snam-ca (rw,path="snam-ca.pem")
      /etc/ssl/snam-certs/lab from cert-lab (rw)
      /operator from rabbitmq-plugins (rw)
      /var/lib/rabbitmq/ from rabbitmq-erlang-cookie (rw)
      /var/lib/rabbitmq/mnesia/ from persistence (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-68pdx (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  persistence:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  persistence-broker-server-0
    ReadOnly:   false
  cert-lab:
    Type:                Projected (a volume that contains injected data from multiple sources)
    SecretName:          rabbitmq-tls-secret
    SecretOptionalName:  <nil>
  ca:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      ca
    Optional:  false
  plugins-conf:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      broker-plugins-conf
    Optional:  false
  rabbitmq-confd:
    Type:                Projected (a volume that contains injected data from multiple sources)
    ConfigMapName:       broker-server-conf
    ConfigMapOptional:   <nil>
    SecretName:          broker-default-user
    SecretOptionalName:  <nil>
  rabbitmq-erlang-cookie:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
  erlang-cookie-secret:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  broker-erlang-cookie
    Optional:    false
  rabbitmq-plugins:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
  pod-info:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.labels['skipPreStopChecks'] -> skipPreStopChecks
  rabbitmq-tls:
    Type:                Projected (a volume that contains injected data from multiple sources)
    SecretName:          rabbitmq-tls-secret
    SecretOptionalName:  0xc001981da8
  kube-api-access-68pdx:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Guaranteed
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                  Age    From                     Message
  ----     ------                  ----   ----                     -------
  Normal   Scheduled               9m43s  default-scheduler        Successfully assigned broker/broker-server-0 to aks-agentpool-26816451-vmss000002
  Normal   SuccessfulAttachVolume  9m31s  attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-536be057-a25b-4478-8d3f-f482636fe622"
  Normal   Pulled                  9m28s  kubelet                  Container image "rabbitmq:3.9.13-management" already present on machine
  Normal   Created                 9m28s  kubelet                  Created container setup-container
  Normal   Started                 9m28s  kubelet                  Started container setup-container
  Normal   Pulled                  9m27s  kubelet                  Container image "rabbitmq:3.9.13-management" already present on machine
  Normal   Created                 9m27s  kubelet                  Created container rabbitmq
  Normal   Started                 9m27s  kubelet                  Started container rabbitmq
  Warning  Unhealthy               9m13s  kubelet                  Readiness probe failed: dial tcp 10.244.1.7:5671: connect: connection refused

[ChunyiLyu]

Hi @padowla, I think the README was updated to match the latest main branch. This is just released in cluster operator 1.13.0.

In the future, if you need to deploy a specific version of RabbitMQ, you can customize spec.image for any RabbitmqCluster you wish to deploy. Alternatively, you can also set a default image in the cluster operator level. See:

• https://www.rabbitmq.com/kubernetes/operator/using-operator.html#images
• https://www.rabbitmq.com/kubernetes/operator/configure-operator-defaults.html Parameter DEFAULT_RABBITMQ_IMAGE

Available RabbitMQ images provided by dockerhub can be found here.