-
Notifications
You must be signed in to change notification settings - Fork 462
[release-4.3] Bug 1801824: kubelet: add more system reservation to protect node #1458
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
[release-4.3] Bug 1801824: kubelet: add more system reservation to protect node #1458
Conversation
|
@rphillips: This pull request references Bugzilla bug 1801824, which is invalid:
Comment DetailsIn response to this:
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. |
|
/lgtm |
|
@rphillips: you cannot LGTM your own PR. DetailsIn response to this:
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. |
|
/hold |
|
@rphillips: This pull request references Bugzilla bug 1801824, which is invalid:
Comment DetailsIn response to this:
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. |
1884020 to
23663a3
Compare
|
/hold cancel |
|
@rphillips: This pull request references Bugzilla bug 1801824, which is invalid:
Comment DetailsIn response to this:
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. |
|
/bugzilla refresh |
|
@rphillips: This pull request references Bugzilla bug 1801824, which is invalid:
Comment DetailsIn response to this:
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. |
|
/lgtm |
|
/retest |
1 similar comment
|
/retest |
|
/skip |
|
/hold |
|
The first comment needs to explain why we are doing this. How it fixes what it fixes etc. If I look in a git log I need to be convinced this is the right thing to have done. |
|
@rphillips: This pull request references Bugzilla bug 1801824, which is invalid:
Comment DetailsIn response to this:
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. |
|
@eparis updated |
|
/bugzilla refresh |
|
@rphillips: This pull request references Bugzilla bug 1801824, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
DetailsIn response to this:
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. |
|
/hold cancel |
this reserves more system reserved headroom for kubelet, crio, and the kernel to safely operate in.
23663a3 to
ab2ee0c
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, kikisdeliveryservice, mrunalp, rphillips The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
After a lengthy Slack conversation @smarterclayton @jim-minter and @rphillips have made a strong case for this change even if the full details of the telemetry examination didn't make it into the commit message. In the future we should make sure that sort of analysis which justifies clawing back 500MiB of memory is safe to do makes it into git commit. cherry-pick-approved |
/test e2e-gcp-upgrade |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@rphillips: All pull requests linked via external trackers have merged: openshift/machine-config-operator#1458. Bugzilla bug 1801824 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
Cherry pick of: #1450
Kubelet and Crio are running at around 250-500 MB each (on default installs). This PR bumps the limit to 1 GB to allow for a bit of headroom to preserve some of the Kernel cache as well. If we don't bump the limit then memory pressure on the node could flush some of the kernel cache resulting in the kernel trying to re-read the cache. This flood of IOPS can be throttled by the cloud providers which results in a kernel pause.
- What I did
- How to verify it
- Description for the changelog