8 Commits (1cee8c45d6c7038fedf542f424ee85af68748147)

Author	SHA1	Message	Date
Chao Xu	5e1adf91df	cmd/kubelet	2016-11-23 15:53:09 -08:00
derekwaynecarr	aeed9cab5e	Fix edge case in qos evaluation	2016-10-10 18:46:06 -04:00
Vishnu kannan	5d4ee244d3	ignore non first class QoS resources from computing Pod Qos ... Signed-off-by: Vishnu kannan <vishnuk@google.com>	2016-09-20 11:19:31 -07:00
k8s-merge-robot	793b4fea9e	Merge pull request #27900 from derekwaynecarr/test_defaults_qos ... Automatic merge from submit-queue Add additional testing scenarios for compute resource requests=0 I was asked about the qos tier of a pod that specified `--requests=cpu=0,memory=0 --limits=cpu=100m,memory=1Gi` and in just investigating current behavior, realized we should have an explicit test case to ensure that 0 values are preserved in defaulting passes, and that this is still a burstable pod (but the lowest for that tier as it related to eviction) /cc @vishh	2016-07-01 16:16:23 -07:00
David McMahon	ef0c9f0c5b	Remove "All rights reserved" from all the headers.	2016-06-29 17:47:36 -07:00
derekwaynecarr	a04e6f8635	Add additional testing scenarios for compute resource requests=0	2016-06-27 14:38:55 -04:00
Buddha Prakash	4acb64f8bd	Make Qos naming consistent across the codebase	2016-06-26 16:19:47 -07:00
Buddha Prakash	c3551ae6cd	Refactor qos package ... Signed-off-by: Buddha Prakash <buddhap@google.com>	2016-06-24 15:36:04 -07:00