Not able to build a fully running cluster

[pavel-spacil]

Hi all,
I'm trying to deploy the 3-node rabbitmq cluster while using the kubernetes-cluster-operator on AWS EKS (v1.29) and the cluster never has all 3 nodes joined together.

The cluster operator is deployed via Helm by bitnami without any additional configuration at version 4.2.3.
I'm trying to deploy basically the production-ready example with a EBS-based Storage Class and without topologySpreadConstraints. However the nodes fail to build up a fully running 3-node cluster. Most of the time I get 2+1 nodes and sometimes 1+1+1.
The rabbitmq is running on version 4.0.2-debian-12-r0, just to mention that.
I've also lowered the DNS cache to 5 secs, as advised in the doc, but still no success.
One startup flow as an example:

• All 3 pods start at the very same time, the -0gets started first based on logs, the -1 as a second and did not join the -0. The -2 hangs in Starting RabbitMQ in background... and after timeout/restart it starts and join -0...

I went thru many issues here and there and did not find any clue how to fix that, whole infrastructure is deployed thru TF so manual actions to rejoin might be problematic to do so...

Is there something else to check or I got misconfigured? 🙏

[pavel-spacil]

Nah, just tried few times with vanilla rabbitmq image from DockerHub and it works as it should....

I will raise this with a bitnami team