You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You should consider using rabbitmq-autocluster plugin to create the clusters, instead CLUSTER_WITH variable
CLUSTER_WITH needs a node to bind the other nodes, with rabbitmq-autocluster you can use different backends and bind the nodes dynamically. So you don't need a "master cluster node".
Currently, it supports:
AWS EC2 tags
AWS Autoscaling Groups
Kubernetes
DNS A records
Consul
etcd
There are a couple of examples to use it on Kubernetes:
Sorry for the long delay. We'd rather keep the scripts and config in the image as minimal as possible. See also #202 (comment) and linked issues.
Since the introduction of the 3.7 image, you can supply /etc/rabbitmq/rabbitmq.conf and the entrypoint will only add/sed supplied envs while leaving other lines in the file untouched (#197 (comment)).
CLUSTER_WITH should take a host name and upon finding a hostname with that name, it should cluster with that node
The text was updated successfully, but these errors were encountered: