|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * rosa_cluster_admin/rosa-cluster-autoscaling.adoc |
| 4 | +:_content-type: REFERENCE |
| 5 | +[id="rosa-cluster-autoscale-settings_{context}"] |
| 6 | += Cluster autoscaling settings using OpenShift Cluster Manager |
| 7 | + |
| 8 | +The tables explain all the configurable UI settings when using cluster autoscaling with OpenShift Cluster Manager. |
| 9 | + |
| 10 | +== Balancing behavior |
| 11 | + |
| 12 | +[cols="4",options="header"] |
| 13 | +|=== |
| 14 | +|Setting |
| 15 | +|Description |
| 16 | +|Type or Range |
| 17 | +|Default |
| 18 | + |
| 19 | +|`balanceSimilarNodeGroups` |
| 20 | +|If `true`, this setting automatically identifies node groups with the same instance type and the same set of labels and tries to keep the respective sizes of those node groups balanced. |
| 21 | +|`boolean` |
| 22 | +|false |
| 23 | + |
| 24 | +|`logVerbosity` |
| 25 | +|Sets the autoscaler log level. Default value is 1, level 4 is recommended for debugging and level 6 enables almost everything. |
| 26 | +|`integer` |
| 27 | +|1 |
| 28 | + |
| 29 | +|`maxPodGracePeriod` |
| 30 | +|Gives pods graceful termination time before scaling down. |
| 31 | +|`integer` |
| 32 | +|600 |
| 33 | + |
| 34 | +|`skipNodesWithLocalStorage` |
| 35 | +|If `true`, the cluster autoscaler never deletes nodes with pods with local storage, e.g. EmptyDir or HostPath. |
| 36 | +|`boolean` |
| 37 | +|true |
| 38 | +|=== |
| 39 | + |
| 40 | +== Resource limits |
| 41 | + |
| 42 | +[cols="4",options="header"] |
| 43 | +|=== |
| 44 | +|Setting |
| 45 | +|Description |
| 46 | +|Type or Range |
| 47 | +|Default |
| 48 | + |
| 49 | +|`maxNodesTotal` |
| 50 | +|Maximum number of nodes in all node groups. Includes all nodes, not just automatically scaled nodes. The cluster autoscaler does not grow the cluster beyond this number. |
| 51 | +|`integer` |
| 52 | +|0 |
| 53 | + |
| 54 | +|`cores.min` |
| 55 | +|Minimum number of cores in cluster. The cluster autoscaler does not scale the cluster beyond these numbers. |
| 56 | +|`object` |
| 57 | +|1 |
| 58 | + |
| 59 | +|`cores.max` |
| 60 | +|Maximum number of cores in cluster. The cluster autoscaler does not scale the cluster beyond these numbers. |
| 61 | +|`object` |
| 62 | +|320000 |
| 63 | + |
| 64 | +|`memory.min` |
| 65 | +|Minimum number of gigabytes of memory in cluster. The cluster autoscaler does not scale the cluster beyond these numbers. |
| 66 | +|`object` |
| 67 | +|1 |
| 68 | + |
| 69 | +|`memory.max` |
| 70 | +|Maximum number of gigabytes of memory in cluster. The cluster autoscaler does not scale the cluster beyond these numbers. |
| 71 | +|`object` |
| 72 | +|6400000 |
| 73 | +|=== |
| 74 | + |
| 75 | +== Scale down configuration |
| 76 | + |
| 77 | +[cols="4",options="header"] |
| 78 | +|=== |
| 79 | +|Setting |
| 80 | +|Description |
| 81 | +|Type or Range |
| 82 | +|Default |
| 83 | + |
| 84 | +|`enable` |
| 85 | +|Should the cluster autoscaler scale down the cluster. |
| 86 | +|`boolean` |
| 87 | +|`true` |
| 88 | + |
| 89 | +|`scaleDown.unneededTime` |
| 90 | +|How long a node should be unneeded before it is eligible for scale down. |
| 91 | +|`string` |
| 92 | +|10m |
| 93 | + |
| 94 | +|`scaleDown.utilizationThreshold` |
| 95 | +|Node utilization level, defined as sum of requested resources divided by capacity, below which a node can be considered for scale down. |
| 96 | +|`string` |
| 97 | +|0.5 |
| 98 | + |
| 99 | +|`scaleDown.delayAfterAdd` |
| 100 | +|How long after scale up that scale down evaluation resumes. |
| 101 | +|`string` |
| 102 | +|10m |
| 103 | + |
| 104 | +|`scaleDown.delayAfterDelete` |
| 105 | +|How long after node deletion that scale down evaluation resumes. |
| 106 | +|`string` |
| 107 | +|0s |
| 108 | + |
| 109 | +|`scaleDown.delayAfterFailure` |
| 110 | +|How long after scale down failure that scale down evaluation resumes. |
| 111 | +|`string` |
| 112 | +|3m |
| 113 | +|=== |
0 commit comments