Automatic merge from submit-queue.
removed deprecated munge script instructions
There is no `hack/update-munge-docs.sh` script. Documentation should not refer to it.
Automatic merge from submit-queue.
Remove Disk Allocatable Evictions
After https://github.com/kubernetes/kubernetes/issues/52336, which uncovered a bug in disk accounting, I have struggled to see why ephemeral-storage allocatable evictions are necessary.
For CPU and Memory allocatable, enforcing allocatable through cgroups provides protection from being starved of compute resources by user pods.
However, for ephemeral-storage it seems that the node-level enforcement mechanisms are able to prevent the node from running out of disk, and thus prevent impact to system daemons.
Additionally, memory usage metrics read from cgroups or statfs are far more reliable than an aggregation of `du` calls which may be collected at different times (as https://github.com/kubernetes/kubernetes/issues/52336 demonstrated).
(As a side note, we should read from the /kubepods cgroup to determine allocatable memory usage)
We should still keep the scheduling aspects of node allocatable for ephemeral storage, as this allows for proper accounting. But I would like to remove enforcement of node allocatable for ephemeral storage.
cc @dchen1107 @derekwaynecarr @jingxu97 @vishh @saad-ali
@kubernetes/sig-node-proposals
Automatic merge from submit-queue.
Add sig labels and use aliases in OWNERS files
This PR does the following:
- Creates a sig-*-leads alias for all sigs and working groups
- Replaces the reviewers/approvers in the sig folders and design-proposals folders with that alias
- Adds a label field to the OWNERS files to allow for automatic sig labelling (https://github.com/kubernetes/test-infra/pull/3502)
Automatic merge from submit-queue.
Simplify Container Status for Ephemeral Containers proposal
This leaves reporting command & args of Ephemeral Containers for a future proposal.
Automatic merge from submit-queue.
Update priority eviction docs
After discussion with @dchen1107 and @bsalamat I think it would be simpler to start with a tiered eviction sorting rather than by using a function. See https://github.com/kubernetes/community/pull/846#pullrequestreview-66920328 for some of the rationale.
This PR makes two changes:
1. Changes the release at which changes take effect to 1.9 (since implementation missed 1.8)
2. Changes the strategy from (usage > requests, func(priority, usage - requests)) to (usage > requests, priority, usage - requests)
cc @dchen1107 @derekwaynecarr @vishh