Add CPUManager policy option to distribute CPUs across NUMA nodes instead of packing them

[klueska]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Add CPUManager policy option to distribute CPUs across NUMA nodes instead of packing them

• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2902-cpumanager-distribute-cpus-policy-option/README.md

• Discussion Link:
  There is no public discussion of this. Only private slack messages with @ffromani and @swatisehgal

• Primary contact (assignee):
  @klueska

• Responsible SIGs:
  /sig node

• Enhancement target (which target equals to which milestone):

  • Alpha release target (1.23):
  • Beta release target (1.33):
  • Stable release target (1.?):

• Alpha

  • KEP (k/enhancements) update PR(s):
    KEP-2902: Add CPUManager policy option to distribute CPUs across NUMA nodes instead of packing them #2904
  • Code (k/k) update PR(s):
    Add CPUManager policy option to distribute CPUs across NUMA nodes instead of packing them kubernetes#105631
  • Docs (k/website) update PR(s):
    Add description of distribute-cpus-across-numa CPUManager policy option website#30468

• Beta

  • KEP (k/enhancements) update PR(s): KEP-2902: Promote CPUManager policy option to distribute CPUs across NUMA nodes to Beta #5117
  • Code (k/k) update PR(s):
    • Add metrics to capture CPU allocation spread across NUMA nodes kubernetes#130491
    • node: cpumgr: e2e: Tests for distribute-cpus-across-numa policy option kubernetes#130498
    • node: cpu-mgr: Graduation of distribute-cpus-across-numa policy option to Beta kubernetes#130541
  • Docs (k/website) update PR(s):
    • node: KEP- 2902: Docs update for Beta graduation website#49901

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

[derekwaynecarr]

/milestone v1.23

[kevindelgado]

Hi @klueska! 1.23 Enhancements team here. Just checking in as we approach enhancements freeze on Thursday 09/09. Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one we would just need the KEP to merge by enhancements freeze :)

Thanks!

[jlbutler]

Hi @klueska 👋 1.23 Docs lead here.

This enhancement is marked as 'Needs Docs' for the 1.23 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu November 18, 11:59 PM PDT.

Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thanks!

[kevindelgado]

Hi @klueska 👋

Checking in once more as we approach 1.23 code freeze at 6:00 pm PST on Tuesday, November 16.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.
• Have a documentation placeholder PR open by Thursday, November 18.

As always, we are here to help should questions come up.

Thanks!!

[klueska]

@kevindelgado website PR created and linked in description