From 498647c4388636ccbbabb9fdbdc4f9f2aba67072 Mon Sep 17 00:00:00 2001 From: Sam Wheating Date: Mon, 26 Jul 2021 09:17:10 -0700 Subject: [PATCH] Removing paragraph about ReplicationController --- .../docs/tasks/run-application/horizontal-pod-autoscale.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md index bc32cf97f2..f1d008edce 100644 --- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md +++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale.md @@ -210,11 +210,6 @@ If you perform a rolling update of a StatefulSet that has an autoscaled number o replicas, the StatefulSet directly manages its set of Pods (there is no intermediate resource similar to ReplicaSet). -Horizontal Pod Autoscaler does not work with rolling update using direct manipulation of replication controllers, -i.e. you cannot bind a Horizontal Pod Autoscaler to a replication controller and do rolling update. -The reason this doesn't work is that when rolling update creates a new replication controller, -the Horizontal Pod Autoscaler will not be bound to the new replication controller. - ## Support for cooldown/delay When managing the scale of a group of replicas using the Horizontal Pod Autoscaler,