-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Memory QoS Beta Update and Production Readiness #4093
Conversation
35e2887
to
f90865e
Compare
/retest |
/lgtm Thank you for the updates! /assign @mrunalp |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Biggest thing I see is we need the metric for beta.
@@ -538,7 +546,7 @@ Pick one of these and delete the rest. | |||
Any change of default behavior may be surprising to users or break existing | |||
automations, so be extremely careful here. | |||
--> | |||
Yes, the kubelet will set `memory.min` for Guaranteed and Burstable pod/container level cgroup. It also will set `memory.high` for burstable container, which may cause memory allocation throttle. `memory.min` for qos or node level cgroup will be set when `--cgroups-per-qos` or `--enforce-node-allocatable` is satisfied. | |||
Yes, the kubelet will set `memory.min` for Guaranteed and Burstable pod/container level cgroup. It also will set `memory.high` for burstable and best effort containers, which may cause memory allocation throttle. `memory.min` for qos or node level cgroup will be set when `--cgroups-per-qos` or `--enforce-node-allocatable` is satisfied. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How will this throttling impact the workloads? (you can answer here or below).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
/lgtm lgtm on the recent updates, and adding new metric in beta as suggested in #4093 (comment) |
Ok, PRR seems fine but it does need SIG approval still |
/assign @SergeyKanzhelev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
@johnbelamaric this lgtm, I'll find official approver shortly
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dchen1107, johnbelamaric, mrunalp, ndixita, SergeyKanzhelev 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 |
One-line PR description: Update KEP for Beta implementation of MemoryQoS feature
Issue link: Support memory qos with cgroups v2 #2570
/assign @bobbypage
/assign @johnbelamaric
/assign @mrunalp
/assign @pacoxu