Tracking in upstream Strimzi issue here [1]

Cruise Control optimization proposals based on goals related to CPU and Network I/0 will only be accurate if a user properly configures broker capacity limits for CPU and Network I/O in their Kafka custom resource. Therefore, Strimzi should only enable these CPU and Network related resource goals when spec.kafka.resources and .spec.cruiseControl.brokerCapacity [2] are explicitly configured by the user in their Kafka custom resource.

This task would require adding logic to the Strimzi Cluster Operator to check if spec.kafka.resources and .spec.cruiseControl.brokerCapacity are explicitly configured in a Kafka custom resource before enabling the following goals in the Cruise Control configuration. [1]

• com.linkedin.kafka.cruisecontrol.analyzer.goals.CpuCapacityGoal
• com.linkedin.kafka.cruisecontrol.analyzer.goals.CpuUsageDistributionGoal
• com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkInboundCapacityGoal
• com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkOutboundCapacityGoal
• com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkInboundUsageDistributionGoal
• com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkOutboundUsageDistributionGoal
• com.linkedin.kafka.cruisecontrol.analyzer.goals.PotentialNwOutGoal}}

If these resource and capacity settings are not explicitly configured, these goals should not be included in the Strimzi-provided goals list by default. This will help users avoid receiving inaccurate, nonsensical optimization proposals from Cruise Control.

[0] https://github.com/strimzi/strimzi-kafka-operator/issues/11409

[1] https://github.com/strimzi/strimzi-kafka-operator/blob/main/cluster-operator/src/main/java/io/strimzi/operator/cluster/model/cruisecontrol/CruiseControlConfiguration.java#L29
[2] https://strimzi.io/docs/operators/latest/configuring.html#property-cruise-control-broker-capacity-reference