diff options
| author | k8s-merge-robot <k8s.production.user@gmail.com> | 2016-05-20 22:58:04 -0700 |
|---|---|---|
| committer | k8s-merge-robot <k8s.production.user@gmail.com> | 2016-05-20 22:58:04 -0700 |
| commit | cebf495b522ee9e4694907bb9d1992cb2a54126c (patch) | |
| tree | c9eb7601338a7fb423981b9c623e12fa01feadde /scripts | |
| parent | ed6788686f7c289aed818f3af23fea7c704d7613 (diff) | |
| parent | c90ed7e246e02dcabce874c767dee28c24bb53e4 (diff) | |
Merge pull request #14943 from vishh/qos
Automatic merge from submit-queue
Updaing QoS policy to be at the pod level
Quality of Service will be derived from an entire Pod Spec, instead of being derived from resource specifications of individual resources per-container.
A Pod is `Guaranteed` iff all its containers have limits == requests for all the first-class resources (cpu, memory as of now).
A Pod is `BestEffort` iff requests & limits are not specified for any resource across all containers.
A Pod is `Burstable` otherwise.
Note: Existing pods might be more susceptible to OOM Kills on the node due to this PR! To protect pods from being OOM killed on the node, set `limits` for all resources across all containers in a pod.
<!-- Reviewable:start -->
---
This change is [<img src="http://reviewable.k8s.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](http://reviewable.k8s.io/reviews/kubernetes/kubernetes/14943)
<!-- Reviewable:end -->
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions