Skip to content

Commit e4d7ffb

Browse files
SamWheatingTim Bannister
andauthored
Update content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
Co-authored-by: Tim Bannister <[email protected]>
1 parent 51c621a commit e4d7ffb

File tree

1 file changed

+11
-2
lines changed

1 file changed

+11
-2
lines changed

content/en/docs/tasks/run-application/horizontal-pod-autoscale.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -198,8 +198,17 @@ The detailed documentation of `kubectl autoscale` can be found [here](/docs/refe
198198

199199
## Autoscaling during rolling update
200200

201-
Currently in Kubernetes, a rolling update is performed using a deployment object, which manages the underlying replica sets for you.
202-
A Horizontal Pod Autoscaler is bound to a single deployment object - it sets the size for the deployment object, and the deployment is responsible for setting sizes of underlying replica sets.
201+
Kubernetes lets you perform a rolling update on a Deployment. In that
202+
case, the Deployment manages the underlying ReplicaSets for you.
203+
When you configure autoscaling for a Deployment, you bind a
204+
HorizontalPodAutoscaler to a single Deployment. The HorizontalPodAutoscaler
205+
manages the `replicas` field of the Deployment. The deployment controller is responsible
206+
for setting the `replicas` of the underlying ReplicaSets so that they add up to a suitable
207+
number during the rollout and also afterwards.
208+
209+
If you perform a rolling update of a StatefulSet that has an autoscaled number of
210+
replicas, the StatefulSet directly manages its set of Pods (there is no intermediate resource
211+
similar to ReplicaSet).
203212

204213
Horizontal Pod Autoscaler does not work with rolling update using direct manipulation of replication controllers,
205214
i.e. you cannot bind a Horizontal Pod Autoscaler to a replication controller and do rolling update.

0 commit comments

Comments
 (0)