Update horizontal-pod-autoscale.md
to make clear that rolling updates only work together with replica sets (via deployments) and not replication controllers.pull/6801/head
parent
fbd0ce69b7
commit
f7846c4469
|
@ -98,9 +98,9 @@ The detailed documentation of `kubectl autoscale` can be found [here](/docs/user
|
||||||
## Autoscaling during rolling update
|
## Autoscaling during rolling update
|
||||||
|
|
||||||
Currently in Kubernetes, it is possible to perform a [rolling update](/docs/tasks/run-application/rolling-update-replication-controller/) by managing replication controllers directly,
|
Currently in Kubernetes, it is possible to perform a [rolling update](/docs/tasks/run-application/rolling-update-replication-controller/) by managing replication controllers directly,
|
||||||
or by using the deployment object, which manages the underlying replication controllers for you.
|
or by using the deployment object, which manages the underlying replica sets for you.
|
||||||
Horizontal Pod Autoscaler only supports the latter approach: the Horizontal Pod Autoscaler is bound to the deployment object,
|
Horizontal Pod Autoscaler only supports the latter approach: the Horizontal Pod Autoscaler is bound to the deployment object,
|
||||||
it sets the size for the deployment object, and the deployment is responsible for setting sizes of underlying replication controllers.
|
it sets the size for the deployment object, and the deployment is responsible for setting sizes of underlying replica sets.
|
||||||
|
|
||||||
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 (e.g. using `kubectl rolling-update`).
|
i.e. you cannot bind a Horizontal Pod Autoscaler to a replication controller and do rolling update (e.g. using `kubectl rolling-update`).
|
||||||
|
|
Loading…
Reference in New Issue