rabbitmq / messaging-topology-operator

RabbitMQ messaging topology operator
Mozilla Public License 2.0
129 stars 65 forks source link

Federation not working for quorum #848

Closed DhawalV closed 3 months ago

DhawalV commented 3 months ago

I've deployed a 3-node RabbitMQ (RMQ) cluster and operator on an AKS cluster. Here are the versions:

RMQ: 3.13.2-management RMQ Cluster Operator: rabbitmqoperator/cluster-operator:2.9.0 Messaging Topology Operator: rabbitmqoperator/messaging-topology-operator:1.14.2 MTLS (Mutual TLS) is enabled downstream, with certificates provided upstream.

Since classic queues are deprecated, we upgraded to quorum queues. Our previous federation configuration (YAML snippet included below) resulted in an error. The created federation link in the upstream queue referenced classic queues, while all actual queues are quorum type. Additionally, both upstream and downstream vhosts have a defaultQueueType of quorum.

The federation works correctly when configured through the dashboard with the queue type set to quorum. However, including "queue: quorum" in the YAML file doesn't seem to apply the configuration, even though there are no errors during deployment.

Request:

Please advise on how to specify the queue type as "quorum" within the YAML file for federation configuration. Your prompt assistance is appreciated.

Original YAML Snippet:

apiVersion: rabbitmq.com/v1beta1 kind: Federation metadata: name: federation-example spec: name: "origin" vhost: "downstream" uriSecret: name: federation-uri ackMode: "on-confirm" rabbitmqClusterReference: name: example-rabbit

Zerpet commented 3 months ago

Duplicate of #844