KEP-4622: Add a TopologyManager policy option for MaxAllowableNUMANodes #4622
Assignees
Labels
lead-opted-in
Denotes that an issue has been opted in to a release
sig/node
Categorizes an issue or PR as relevant to SIG Node.
stage/alpha
Denotes an issue tracking an enhancement targeted for Alpha status
Milestone
Comments
k8s-ci-robot
added
the
needs-sig
|
/sig node |
k8s-ci-robot
added
sig/node
cyclinder
changed the title
|
/assign @cyclinder |
|
I've added this to the tracking sheet for 1.31: |
|
/label lead-opted-in |
k8s-ci-robot
added
the
stage/alpha
k8s-ci-robot
added
the
lead-opted-in
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: TBD
Discussion Link: kubelet: Add a flag "MaxAllowableNUMANodes" kubernetes#124148 (comment)
Primary contact (assignee): @klueska @ffromani
Responsible SIGs: /sig node
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements) update PR(s): KEP-4622: New TopologyManager Policy: max-allowable-numa-nodes #4624k/k) update PR(s): kubelet: Add a flag "MaxAllowableNUMANodes" kubernetes#124148k/website) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
Tasks
The text was updated successfully, but these errors were encountered: