Rebalance queues after initial cluster startup

[mkuratczyk]

In https://github.com/rabbitmq/cluster-operator/pull/385 we implemented queue rebalancing after a rolling restart. However, if definitions are imported through configuration, even a newly deployed cluster may be unbalanced. It is therefore worth rebalancing it after the initial deployment.

While we could add a condition to only do that if definitions are imported, I don't think it's worth it - if they are not, the command will simply execute very quickly as there will be nothing to do.

[mkuratczyk]

Perhaps unnecessary if we implement https://github.com/rabbitmq/cluster-operator/issues/631

[github-actions[bot]]

This issue has been marked as stale due to 60 days of inactivity. Stale issues will be closed after a further 30 days of inactivity; please remove the stale label in order to prevent this occurring.

[github-actions[bot]]

Closing stale issue due to further inactivity.

[Zerpet]

@mkuratczyk I believe we can close this issue given that this was fixed in the core. WDYT?

https://github.com/rabbitmq/cluster-operator/issues/631#issuecomment-1096554711

[mkuratczyk]

Indeed. While validating it works as expected, I updated the import-by-URL example. The leader are well balanced after deploying this example.