Comment 3 for bug 1815196

So my concern is similar to the problem for rabbitmq-server in LP#1818260. If the cluster is acting on its own to remove units independent of the charm. During deploy time when resources are scarce we are likely to hit false positives and have units removed.

Sounds like we need to discuss this change a bit further.

In the meantime, at a minimum for [0], we would need the action to re-add a node and verbiage in the config option that warns the user the cluster acting on its own could cause problems.

The approach being taken for rabbit will be to ignore the config option during deploy time and only after the cluster is complete add the configuration. This still leaves us vulnerable to the cluster acting before we are ready but it helps mitigate the problem.

[0] https://review.opendev.org/#/c/649083/