-
Notifications
You must be signed in to change notification settings - Fork 1.5k
KEP-3953: Node Resource Hot Plug #3955
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: master
Are you sure you want to change the base?
Conversation
a7bc843
to
03e927f
Compare
/assign @mrunalp @SergeyKanzhelev @klueska |
/cc |
/cc |
/cc |
yeah, I will reach out, if there are any changes in future, Thank you for taking a look. |
Thanks for the review, We plan to provide compatibility with autoscaler by storing the initial node resource in node object and also plan to provide this feature during beta graduation so we can get started now. But we are open for community feedback. Thank you. |
Sounds good to me, thanks! |
gave a read of the kep, no comments or suggestions currently, but happy to see this work progressing. |
Co-authored-by: kishen-v <kishen.viswanathan@ibm.com>
Co-authored-by: kishen-v <kishen.viswanathan@ibm.com>
Co-authored-by: kishen-v <kishen.viswanathan@ibm.com>
Co-authored-by: kishen-v <kishen.viswanathan@ibm.com>
Co-authored-by: kishen-v <kishen.viswanathan@ibm.com>
Co-authored-by: kishen-v <kishen.viswanathan@ibm.com>
* Enable the re-initialization of resource managers (CPU manager, memory manager) and kube runtime manager without reset to accommodate alterations in the node's resource allocation. | ||
* Recalculating and updating swap memory limit for existing pods. | ||
|
||
### Non-Goals |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really see you call out devices. Is this in scope for this feature? ie adding gpudevices?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No its not in the scope, May be I can explicitly mention that for more clarity, Thanks.
AFAIU this is only for CPU and Memory what about hot-plug of PCIe devices? How will this work once we have cAdvisorless metrics? #2371 |
Yes correct, PCIe devices are out of scope for this KEP, About cAdvisorless metrics would seek help from @haircommander. |
node level metrics aren't covered by 2371 so we should be good there, but regardless of the source if we're going through the stats manager then there should be no difference |
Uh oh!
There was an error while loading. Please reload this page.