Improved multi-numa alignment in Topology Manager

[klueska]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  An enhancement to the TopologyManager that considers relative distances between NUMA nodes when calculating "best hints" that include more than one NUMA node.

• Kubernetes Enhancement Proposal:
  https://.com/kubernetes/enhancements/blob/master/keps/sig-node/3545-improved-multi-numa-alignment/README.md

• Discussion Link:
  Private slack messages

• Primary contact (assignee):
  @PiotrProkop

• Responsible SIGs:
  /sig node

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

  • Alpha release target: 1.26
  • Beta release target: 1.28
  • Stable release target: 1.32

• Alpha

  • KEP (k/enhancements) update PR(s):
    KEP-3545: Improved multi-numa alignment in Topology Manager #3549
  • Code (k/k) update PR(s):
    node: topologymanager: Improved multi-numa alignment in Topology Manager kubernetes#112914
  • Docs (k/website) update PR(s):
    topologymanager: document topology manager policy options website#37668

• Beta

  • KEP (k/enhancements) update PR(s):
    Promote Improved multi-numa alignment in Topology Manager to beta #4079
  • Code (k/k) update PR(s):
    topologymanager: Promote support for improved multi-numa alignment in Topology Manager to beta kubernetes#118816
  • Docs (k/website) update(s):
    topologymanager: document topology manager policy options promotion to beta  website#41718

• Stable:

  • KEP (k/enhancements) update PR(s):
    KEP-3545: graduate to GA #4882
  • Code (k/k) update PR(s):
    add e2e tests for prefer-closest-numa-nodes TopologyManagerPolicyOption kubernetes#127922
    topologymanager: Promote support for improved multi-numa alignment in Topology Manager to GA kubernetes#128124
  • Docs (k/website) update(s):
    topology-manager: promoto TopologyManagerPolicyOptions to stable website#48339

[klueska]

/cc @fromanirh
/cc @swatisehgal

[ffromani]

thanks for the heads up, I'll review shortly

[derekwaynecarr]

/label lead-opted-in

[Atharva-Shinde]

Hey @klueska 👋, 1.26 Enhancements team here!

Just checking in as we approach Enhancements Freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26

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 an updated detailed 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.

For this KEP, we would just need to:
-Get the PR #3549 merged before Enhancements Freeze to make this enhancement eligible for 1.26 release.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well.
Thank you :)

[Atharva-Shinde]

/milestone v1.26
/label tracked/yes

[k8s-ci-robot]

@Atharva-Shinde: You must be a member of the kubernetes/milestone-maintainers team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.26
/label tracked/yes

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Atharva-Shinde]

/stage alpha