Beata Skiba e5f8bfa023 Do not count failed pods as unready in HPA controller ... Currently, when performing a scale up, any failed pods (which can be present for example in case of evictions performed by kubelet) will be treated as unready. Unready pods are treated as if they had 0% utilization which will slow down or even block scale up. After this change, failed pods are ignored in all calculations. This way they do not influence neither scale up nor scale down replica calculations.		2018-03-01 16:21:02 +01:00
..
metrics	Implement external metrics in HPA	2018-02-27 14:10:29 +01:00
BUILD	Implement external metrics in HPA	2018-02-27 14:10:29 +01:00
OWNERS	Add approvers to owners file for hpa	2017-07-18 13:23:43 +02:00
doc.go	Use Go canonical import paths	2016-07-16 13:48:21 -04:00
horizontal.go	Implement external metrics in HPA	2018-02-27 14:10:29 +01:00
horizontal_test.go	Do not count failed pods as unready in HPA controller	2018-03-01 16:21:02 +01:00
legacy_horizontal_test.go	remove duplicated import	2018-01-17 09:34:59 +08:00
legacy_replica_calculator_test.go	Make HPA tolerance a flag	2017-09-28 22:01:51 -04:00
rate_limitters.go	Fix golint errors in `pkg/controller/podautoscaler`	2017-09-09 14:53:34 -04:00
replica_calculator.go	Do not count failed pods as unready in HPA controller	2018-03-01 16:21:02 +01:00
replica_calculator_test.go	Do not count failed pods as unready in HPA controller	2018-03-01 16:21:02 +01:00