New Static Policy Proposal - Spread HT across physical CPUs

[Jeffwan]

Enhancement Description

• One-line enhancement description (can be used as a release note): VPA + core binding
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy/README.md
• Discussion Link: https://docs.google.com/document/d/1V3DLh3pH3CD-xhhJvAnOq_oWgPyjO-vj6wY6qdew9H0/edit#heading=h.ybybfdfputt
• Primary contact (assignee): @Jeffwan
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.31
  • Beta release target (x.y): 1.33?
  • Stable release target (x.y): 1.35
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4176: A Static Policy Option to spread hyperthreads across physical CPUs #4177
    • node: 4176: update milestones for 1.31 #4731
  • Code (k/k) update PR(s): KEP-4176: Add a new static policy SpreadPhysicalCPUsPreferredOption kubernetes#123733
  • Docs (k/website) update PR(s): Add docs for KEP-4176 new static policy DistributeCPUsAcrossCores website#47014 (comment)

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[Jeffwan]

/sig node

[ffromani]

/cc

[SergeyKanzhelev]

/stage alpha
/milestone v1.29

Applying the milestone as discussed at SIG Node meeting this week

[npolshakova]

Hello @Jeffwan, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board? Thanks!

[salehsedghpour]

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.29 now,
If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

[Jeffwan]

Sounds good. I will follow the instruction and move it to v1.30. We plan to polish it for further review.

[Jeffwan]

@salehsedghpour This is the initial issue and the PR is not merged yet. Could you help add v1.30 milestone? @SergeyKanzhelev @ffromani We will put some time to address all the comments recently

[salehsedghpour]

Thanks for the info @Jeffwan, may you please follow it up so that you could also have the lead-opted-in label and the milestone with the SIG leads?