openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

updating ClusterAutoscaler

Browse Source
This commit is contained in:
Kathryn Alexander
2019-02-27 13:06:42 -05:00
parent 7cece9a4fe
commit e138a656dd
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
modules/machine-api-overview.adoc
View File

@@ -38,16 +38,16 @@ deletes it, and, on supported platforms, makes a new machine.
`ClusterAutoscaler`:: This resource is based on the upstream
link:https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler[ClusterAutoscaler]
project. In the {product-title} implementation, it is integrated with the
Cluster API by extending the `MachineSet` API.
////
`ClusterAutoscalerOperator`:: Instead of interacting with the `ClusterAutoscaler`
itself, you use its Operator. The `ClusterAutoscalerOperator` manages
the `ClusterAutoscaler` deployment. With this Operator, you can set cluster-wide
scaling limits for resources such as cores, nodes, memory, and GPU.
Cluster API by extending the `MachineSet` API. You can set cluster-wide
scaling limits for resources such as cores, nodes, memory, GPU,
and so on. You can set the priority so that the cluster prioritizes pods so that
new nodes are not brought online for less important pods. You can also set the
ScalingPolicy so you can scale up nodes but not scale them down.
////
`ClusterAutoscalerOperator`:: Instead of interacting with the `ClusterAutoscaler`
itself, you use its Operator. The `ClusterAutoscalerOperator` manages
the `ClusterAutoscaler` deployment.
////
In {product-title} version 3.11, you could not roll out a multi-zone architecture easily because the cluster