Currently, the cluster capacity (number of nodes, their size etc.) in Cruise Control is configured through a Config Map and requires restart of Cruise Control to be reloaded. This can be quite annoying when trying to make Strimzi more elastic (such as Kafka auto-scaling) as Cruise Control needs a rolling update for every change to the cluster size (scale-up, scale-down), its storage (new volumes, etc.) and so on.

It would be nice to be able to reload the configuration dynamically for example through the REST API or by Cruise Control periodically checking some file etc.