[bitnami/rabbitmq-cluster-operator] Not able to build a fully running cluster

Name and Version

bitnami/rabbitmq:4.0.2-debian-12-r0

What architecture are you using?

amd64

What steps will reproduce the bug?

Have an AWS EKS cluster, tried 1.29 as well as 1.30
Deploy rabbitmq-cluster-operator Helm chart by bitnami in version 4.3.24
Define some StorageClass, in my case EBS one
Deploy production-ready example from here with referencing that SC

What is the expected behavior?

The 3-node cluster gets up and running just fine, no isolated node.

What do you see instead?

The nodes don't join together, in most deployments I've got 2+1 configuration (= 2 isolated clusters, one with 2 nodes, second with a just one), but sometimes also 1+1+1, never just 3...

Additional information

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 -0 gets 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...

Tried vanilla rabbitmq:4.0.2 Docker image from dockerhub and it works just fine in all cases.

bitnami / charts