mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 12:43:32 +09:00
The refusal message and the README told the reader to manage users and vhosts outside the chart. That reads as an instruction to move them into hand-written User/Vhost/Permission objects, which fails the same way: the topology operator derives its connection from the RabbitmqCluster, not from who created the CR, so those objects break identically and without the chart's refusal to warn anyone. Say what the flag actually costs — the cluster leaves that operator's reach entirely — and point at rabbitmqctl or a definitions import. Also narrows the claim that no option closes plaintext: a variant through spec.rabbitmq.additionalConfig looks reachable but is not wired or validated here, so it is named as an open question rather than left implicitly denied. Signed-off-by: Aleksei Sviridkin <f@lex.la>