Solly Ross 8337031bf5 Rate limit HPA controller to sync period ...

Since the HPA controller pulls information from an external source that
makes no guarantees about consistency, it's possible for the HPA
to get into an infinite update loop -- if the metrics change with
every query, the HPA controller will run it's normal reconcilation,
post a status update, see that status update itself, fetch new metrics,
and if those metrics are different, post another status update, and
repeat.  This can lead to continuously updating a single HPA.

By rate-limiting each HPA to once per sync interval, we prevent this
from happening.

2017-03-09 16:32:01 -05:00

..

metrics

HPA Controller: Use Custom Metrics API

2017-03-01 10:21:50 -05:00

BUILD

Rate limit HPA controller to sync period

2017-03-09 16:32:01 -05:00

doc.go

Use Go canonical import paths

2016-07-16 13:48:21 -04:00

horizontal_test.go

Rate limit HPA controller to sync period

2017-03-09 16:32:01 -05:00

horizontal.go

Rate limit HPA controller to sync period

2017-03-09 16:32:01 -05:00

legacy_horizontal_test.go

HPA Controller: Use Custom Metrics API

2017-03-01 10:21:50 -05:00

legacy_replica_calculator_test.go

HPA Controller: Use Custom Metrics API

2017-03-01 10:21:50 -05:00

OWNERS

Update OWNERS based on PR comments

2016-11-02 16:28:23 -07:00

rate_limitters.go

Rate limit HPA controller to sync period

2017-03-09 16:32:01 -05:00

replica_calculator_test.go

HPA Controller: Use Custom Metrics API

2017-03-01 10:21:50 -05:00

replica_calculator.go

Convert HPA controller to use autoscaling/v2alpha1

2017-02-16 15:03:14 -05:00