-
Notifications
You must be signed in to change notification settings - Fork 40.9k
[FG:InPlacePodVerticalScaling] Add a feature gate for in-place resize with static memory manager policy support #132473
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
base: master
Are you sure you want to change the base?
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
Hi @pravk03. 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-sigs/prow repository. |
/assign @tallclair |
74129f2
to
0b359bd
Compare
0b359bd
to
cd315c5
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pravk03 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cc @esotsal |
87105d6
to
0390d1e
Compare
Thanks @pravk03 overall looks good to me , beside my comment/suggestion with regard naming of the feature gate. I noticed also that you have added refactoring to add node config in test case and an additional check if pod/container needs resize, nice additions , thanks for that! |
/remove-sig api-machinery |
…y Manager support. New gate "InPlacePodVerticalScalingExclusiveMemory" is off by default, but can be enabled to unblock development of Static Memory Manager policy alongside InPlacePodVerticalScaling.
0390d1e
to
5d4a9bf
Compare
5d4a9bf
to
72bfac4
Compare
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR is to introduce a separate feature gate to enable/disable support for static memory policy. Along with introducing a new feature gate, a check is added to identify if CPU or Memory is being resized and check the appropriate feature gate.
Which issue(s) this PR is related to:
#132466
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: