-
Notifications
You must be signed in to change notification settings - Fork 39.4k
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
Set kube-proxy memory request to 50Mi #118268
Conversation
With optional override using KUBE_PROXY_MEMORY_REQUEST following the KUBE_PROXY_CPU_REQUEST pattern.
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/test-infra repository. |
Hi @jingyuanliang. 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. |
/assign @aojea |
/ok-to-test |
/approve makes sense! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, jingyuanliang 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 label has been added. Git tree hash: f24ea30b76a4b9f7bf128c026ca70cae5257279e
|
/retest |
With optional override using KUBE_PROXY_MEMORY_REQUEST following the KUBE_PROXY_CPU_REQUEST pattern.
What type of PR is this?
/kind feature
What this PR does / why we need it:
When a container doesn't have requests, the scheduler assumes 100mCPU and 200Mi of memory for the purposes of node resources usage scoring. In some scenarios, this can throw off users who are expecting a certain level of bin-packing. With explicit resources requests, the behavior of the scheduler can be more predictable to users.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: