KEP-4622: Add a TopologyManager policy option for MaxAllowableNUMANodes

[cyclinder]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add a config option to the kubelet that allows us to configure the value of maxAllowableNUMANodes in the TopologyManager
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4622-topologymanager-max-allowable-numa-nodes/README.md
• Discussion Link: kubelet: Add a TopologyManager policy option: max-allowable-numa-nodes kubernetes#124148 (comment)
• Primary contact (assignee): @klueska @ffromani @cyclinder
• Responsible SIGs: /sig node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): -
  • Beta release target (x.y): 1.31
  • Stable release target (x.y): 1.35
• Beta
  • KEP (k/enhancements) update PR(s): KEP-4622: New TopologyManager Policy: max-allowable-numa-nodes #4624
  • Code (k/k) update PR(s): kubelet: Add a TopologyManager policy option: max-allowable-numa-nodes kubernetes#124148
  • Docs (k/website) update PR(s): KEP-4622: Add docs for TopologyManager policy option for MaxAllowableNUMANodes website#46870
• Stable
  • KEP (k/enhancements) update PR(s): KEP-4622: promote topologyManager policy: max-allowable-numa-nodes to GA in 1.35 #5627
  • Code (k/k) update PR(s): KEP-4622: promote topology manager max-allowable-numa-nodes to GA kubernetes#134614
  • Docs (k/website) update(s): KEP-4622: node: topology manager max-allowable-numa-nodes is GA website#52843

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

### Tasks
- [x] Feature implemented behind the existing static policy feature flag
- [x] Initial unit tests completed and coverage is improved
- [x] Documents are improved and enough guidance and examples can be given to potential users.
- [x] Add an e2e test to verify the input validation.

[cyclinder]

/sig node

[cyclinder]

/assign @cyclinder

[klueska]

I've added this to the tracking sheet for 1.31:
https://docs.google.com/document/d/1U10J0WwgWXkdYrqWGGvO8iH2HKeerQAlygnqgDgWv4E/edit

[SergeyKanzhelev]

/label lead-opted-in
/milestone v1.31
/stage alpha

[prianna]

Hello @cyclinder @klueska 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting stage alpha for v1.31 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline of Thursday 6th June 2024 so that the PRR team has enough time to review your KEP.

For this KEP, it looks like we still need to do the following:

• Merge KEP-4622: New TopologyManager Policy: max-allowable-numa-nodes #4624 before the enhancement freeze date.
• Update KEP stage to alpha if that's the intended stage, right now it looks as though the KEP is targeting beta for v1.31
• Add graduation criteria for alpha if that's the intended stage targeted

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

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!