Exception request for Enhancement #4622

[Kevin Klues]

Enhancement name:
New TopologyManager Policy: max-allowable-numa-nodes
 

Enhancement status (alpha/beta/stable): beta

SIG: node

k/enhancements repo issue #:
https://github.com/kubernetes/enhancements/pull/4622

PR #’s:

https://github.com/kubernetes/enhancements/pull/4624

Additional time needed (in days): 1 -- already approved by sig-node, only missing PRR approval

Reason this enhancement is critical for this milestone:

Many modern systems have more than 8 NUMA nodes. At present, there is no way for these systems to make use of the TopologyManager without the kubelet crashing. This feature provides a way for these systems to make use of the TopologyManager without crashing.

Risks from adding code late: (to k8s stability, testing, etc.)

Very minimal. This is a single kubelet flag replacing a hard-coded value. No other logic is changing.

Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)

We've had lots of complaints from users running on systems with more than 8 NUMA nodes that they have no way to use this feature, and this flag is providing them with the ability to do so.

Kevin

[Angelos Kolaitis]

Hi all,

The release team is APPROVING this exception request (Slack thread). Your updated deadline to merge all PRs and docs for your KEP is 19:00 PDT Friday, 14th June 2024.

If you need any clarification, please reach out to us in the #sig-release Slack channel.

Thanks,
Angelos Kolaitis
1.31 Release Team Lead