What would you like to be added:

The new option aside from BestFit for balanced placement which tries to "balance" the split for the number of Pods between a pair of domains.

For example, assume we have a Job with 16 Pods which cannot all fit into a single rack, but two.

We found experimentally that the split 8:8 into racks performs better than 1:15.

Some open questions which would be good to clarify:

• what to do if perfect split is not possible, for example, should we go with 9:7 or 10:6?
• is 3 racks "balanced" 6:6:4 better than two skewed 15:1?
• what to do about 2-level scheduling, should we balance at the level of Pods or PodSlices?

We can already start prototyping to guide some of the decisions to see what is easily available and assessing the gain / effort ration.

However, I expect a KEP update with the finalized proposal regarding the open-questions.

We can introduce the new policy behind an Alpha feature gate to collect feedback.

Why is this needed:

To optimize performance by balancing the counts of Pods when possible.