k8s-merge-robot c17465be03 Merge pull request #25531 from ingvagabund/introduce-memory-pressure-to-scheduler ... Automatic merge from submit-queue Introduce node memory pressure condition to scheduler Following the work done by @derekwaynecarr at https://github.com/kubernetes/kubernetes/pull/21274, introducing memory pressure predicate for scheduler. Missing: * write down unit-test * test the implementation At the moment this is a heads up for further discussion how the new node's memory pressure condition should be handled in the generic scheduler. **Additional info** * Based on [1], only best effort pods are subject to filtering. * Based on [2], best effort pods are those pods "iff requests & limits are not specified for any resource across all containers". [1] 542668cc79/docs/proposals/kubelet-eviction.md (scheduler) [2] https://github.com/kubernetes/kubernetes/pull/14943		2016-05-21 19:37:15 -07:00
..
cmd/kube-scheduler	Use protobufs by default to communicate with apiserver	2016-05-21 11:38:32 +02:00
pkg	Merge pull request #25531 from ingvagabund/introduce-memory-pressure-to-scheduler	2016-05-21 19:37:15 -07:00
OWNERS	Move blunderbuss assignees into tree	2016-03-02 20:46:32 -05:00