messaging-topology-operator icon indicating copy to clipboard operation
messaging-topology-operator copied to clipboard

Federation not working for quorum

Open pay-11-m opened this issue 1 year ago • 4 comments

Hi Team,

I have deployed 3 node RMQ cluster and operator on Azure kubernetes cluster.

Versions: RMQ: 3.13.2-management RMQ cluster operator: rabbitmqoperator/cluster-operator:2.9.0 controller-gen.kubebuilder.io/version: v0.14.0 RMQ messaging topology operator: rabbitmqoperator/messaging-topology-operator:1.14.2 controller-gen.kubebuilder.io/version: v0.15.0 mtls is on in downstream, and certificates are given in upstream.

Since classic has been deprecated, we have upgraded to quorum. The federation used before was as below: 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

But it was showing error. The federation link created in Upstream queue refers to classic, whereas all the queues are in quorum. Also the vhost in both Upstream and downstream have defaultQueueType is quorum.

Could you please support?

But when I added it through dashboard, and applied queuetype as quorum, it is working fine. But, how can I add queuetype in yaml file. I added as below but even if it didn't show any error while applying, it is not taking that configuration. apiVersion: rabbitmq.com/v1beta1 kind: Federation metadata: name: federation-example spec: name: "origin" vhost: "downstream" queue: quorum

I would really appreciate if you could support at earliest.

pay-11-m avatar Jun 26 '24 02:06 pay-11-m