-
Notifications
You must be signed in to change notification settings - Fork 40.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReservedMemory Configuration for NUMA #106840
Conversation
Welcome @rthakur-est! |
Hi @rthakur-est. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/kind bug |
/sig node |
280979a
to
fdeb691
Compare
/ok-to-test |
Kubelet throws error when multiple numa nodes are specified for memory reservation. This is due to "," being used as separator for different memory types within same numa node as well as for different numa nodes. This PR fixes the error by using ";" as the separator for specifying multiple numa node configuration. Signed-off-by: Ravindra Thakur <ravindra.nath.thakur@est.tech>
fdeb691
to
a1f73cc
Compare
/release-note-none |
/priority important-longterm |
/lgtm |
/assign @dchen1107 @lavalamp |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, rthakur-est The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm We need to update the documentation to capture this change. |
/retest |
Kubelet throws error when multiple numa nodes are specified for memory
reservation. This is due to "," being used as separator for different
memory types within same numa node as well as for different numa nodes.
This PR fixes the error by using ";" as the separator for
specifying multiple numa node configuration.
Signed-off-by: Ravindra Thakur ravindra.nath.thakur@est.tech
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #105783
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: