Update content/en/docs/tasks/run-application/horizontal-pod-autoscale.md
Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
@@ -198,8 +198,17 @@ The detailed documentation of `kubectl autoscale` can be found [here](/docs/refe
|
|||||||
|
|
||||||
## Autoscaling during rolling update
|
## Autoscaling during rolling update
|
||||||
|
|
||||||
Currently in Kubernetes, a rolling update is performed using a deployment object, which manages the underlying replica sets for you.
|
Kubernetes lets you perform a rolling update on a Deployment. In that
|
||||||
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.
|
case, the Deployment manages the underlying ReplicaSets for you.
|
||||||
|
When you configure autoscaling for a Deployment, you bind a
|
||||||
|
HorizontalPodAutoscaler to a single Deployment. The HorizontalPodAutoscaler
|
||||||
|
manages the `replicas` field of the Deployment. The deployment controller is responsible
|
||||||
|
for setting the `replicas` of the underlying ReplicaSets so that they add up to a suitable
|
||||||
|
number during the rollout and also afterwards.
|
||||||
|
|
||||||
|
If you perform a rolling update of a StatefulSet that has an autoscaled number of
|
||||||
|
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,
|
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.
|
i.e. you cannot bind a Horizontal Pod Autoscaler to a replication controller and do rolling update.
|
||||||
|
|||||||
Reference in New Issue
Block a user