-
Notifications
You must be signed in to change notification settings - Fork 14.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
Add documentation for disk based eviction #1196
Add documentation for disk based eviction #1196
Conversation
/cc @vishh @ronnielai |
Review status: 0 of 1 files reviewed at latest revision, all discussions resolved. Comments from Reviewable |
|
||
In future releases, the `kubelet` will support the ability to trigger eviction decisions based on disk pressure. | ||
Each of the above signals support either a literal or percentage based value. The percentage based value | ||
is calculated relative to the total capacity associated with each signal. |
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.
Does this hold for memory.available
too?
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.
yes. it holds for all the things.
Review pass complete. |
### How kubelet ranks pods for eviction in response to inode exhaustion | ||
|
||
At this time, it is not possible to know how many inodes were consumed by a particular container. If the `kubelet` observes | ||
inode exhaustion, it will evict pods by ranking them by quality of service. The following issue has been opened in cadvisor |
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 does it rank pods in the same QoS class?
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.
this is addressed under "Known issues" section "How kubelet ranks pods for eviction in response to inode exhaustion", in the future, we want it to rank by consumption when we can know it.
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.
to be clear, it does not differentiate within a class, so its random.
Review status: 0 of 1 files reviewed at latest revision, 12 unresolved discussions. docs/admin/out-of-resource.md, line 40 [r1] (raw file):
|
@derekwaynecarr , have you had a chance to address the comments from @vishh and @timstclair yet? |
@devin-donnelly - I am addressing feedback now. |
docs/admin/out-of-resource.md, line 72 [r1] (raw file):
|
Review status: 0 of 1 files reviewed at latest revision, 12 unresolved discussions. docs/admin/out-of-resource.md, line 49 [r1] (raw file):
|
@vishh @timstclair -- all comments addressed. PTAL, apologies this is 30 min late. |
I am also confused by Reviewable... do you know if we are going to turn it off by default now with github reviews being a thing? |
I would prefer to use GitHub's PR Review system from here on out; it's cleaner than Reviewable. |
Thanks for getting to this, @derekwaynecarr . |
Review status: 0 of 1 files reviewed at latest revision, 12 unresolved discussions. docs/admin/out-of-resource.md, line 223 [r1] (raw file):
|
LGTM |
Review status: 0 of 1 files reviewed at latest revision, 12 unresolved discussions. docs/admin/out-of-resource.md, line 223 [r1] (raw file):
|
@derekwaynecarr , would you mind fixing this last comment in Reviewable about the header levels? Then I'll merge. |
@devin-donnelly -- restructured, headers should be good. |
Looks good. Thanks! I'll merge it into 1.4. |
* add emojivoto policy manifest This PR adds a new file under `run.linkerd.io` to have a `emojivoto` policy manifest, that is maintained and updated based on the changes from `emojivoto.yml` manifest here. This will make it possible to access the policy manifest from `run.linkerd.io/emojivoto-policy.yml` Signed-off-by: Tarun Pothulapati <tarunpothulapati@outlook.com>
Documents new features in eviction.
This change is