Closed the-technat closed 5 months ago
This issue is currently awaiting triage.
If metrics-server contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Hi @the-technat. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Hi @stevehipwell
Yes I did a manual test in our env by setting really low resource requests and let nanny update them. That worked perfectly fine with the patched RoleBinding.
/ok-to-test
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: stevehipwell, the-technat
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Just discovered in our k8s environment that nanny isn't working as expected. Instead of working around this issue by hacking in a custom rolebinding, I thought I'll fix this upstream. The change itself should be really simple and seems to be a leftover of PR #1234.
What this PR does / why we need it: Allows nanny to patch it's deployment and adjust resource limits according to current usage.
Which issue(s) this PR fixes: Fixes #1275