During the most recent Cruise Control issue triage, we discussed the merits of improving CPU-based reporting and rebalancing. It was noted that CPU-based balancing isn’t important for most clusters and the effort required to address the current limitations would not be worth the benefit, making this task the task a low priority.

It was suggested that we revisit disabling the CPU goals by default. As discussed here [2], we would need to provide a good justification to change the default behavior in an proposal, issue, or PR.

CC mmaison@redhat.com rh-ee-tcooper 

[1] https://issues.redhat.com/browse/ENTMQST-6747
[2] https://github.com/strimzi/strimzi-kafka-operator/pull/11465#discussion_r2153139980