diff options
| author | k8s-merge-robot <k8s.production.user@gmail.com> | 2016-05-04 03:06:54 -0700 |
|---|---|---|
| committer | k8s-merge-robot <k8s.production.user@gmail.com> | 2016-05-04 03:06:54 -0700 |
| commit | ff894ce2a20d5ac9377e74b70265b948eb234333 (patch) | |
| tree | 9ed6070afdbe4a69cfdc3a8b07f44b7311f8e953 /node-allocatable.md | |
| parent | 27c6c33ceb36340a1bbc004d219b3bca002dcc6d (diff) | |
| parent | 188b80a2544aea76ba9dbe22d736f7d733a21eec (diff) | |
Merge pull request #18724 from derekwaynecarr/eviction_policy_spec
Automatic merge from submit-queue
Kubelet pod eviction proposal
The following is a proposal for how the `kubelet` may pro-actively fail a pod in response to local compute resources being starved. The proposal focuses on memory as a first candidate, and defines a `greedy` strategy for reclaiming starved resources on the node since it seemed easiest to describe for operators versus other options and probably satisfies a broad set of use case environments.
Putting this out now for community feedback, but anticipate some more refinement around how we report eviction configuration back to users in the `Node API`.
/cc @bgrant0607 @smarterclayton @vishh @dchen1107 @kubernetes/rh-cluster-infra @kubernetes/goog-node
Diffstat (limited to 'node-allocatable.md')
0 files changed, 0 insertions, 0 deletions