-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Reduce CPU and memory requests for Metrics Server Nanny #57252
Conversation
/assign @piosz |
/unassign @DirectXMan12 |
/retest |
2 similar comments
/retest |
/retest |
/assign @x13n |
/unassign @mikedanese |
/lgtm |
50MB of memory seems to be too few for 1000 nodes cluster. @wojtek-t how much memory do we need to list thousands of nodes? |
/lgtm |
Talked offline with Wojciech offline. A single node requires several kilobytes, so for storing 1k nodes several megabytes is enough. I've checked that on 1k node nanny consumes up to ~35MB, which sounds reasonable given that there are other sources of memory usage, binary overhead etc. 50Mi looks like a safe request. |
/approve no-issue |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kawych, piosz, x13n Associated issue requirement bypassed by: piosz The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 57252, 57168). If you want to cherry-pick this change to another branch, please follow the instructions here. |
…-upstream-release-1.9 Automatic merge from submit-queue. Automated cherry pick of #57252: Reduce CPU and memory requests for Metrics Server Nanny Cherry pick of #57252 on release-1.9. #57252: Reduce CPU and memory requests for Metrics Server Nanny **Release note**: ```release-note Free up CPU and memory requested but unused by Metrics Server Pod Nanny. ```
What this PR does / why we need it:
Metrics Server Nanny is a sidecar container that performs small computations every 5 minutes to scale Metrics Server resource requirements when cluster size changes. This change reduces the CPU and memory requests to free up unused resource.
Release note: