You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
update node info processors to include unschedulable nodes (#8520)
* pass allNodes to node info provider Process
This change passes all the nodes to the mixed node info provider
processor that is called from `RunOnce`. The change is to allow
unschedulable and unready nodes to be processed as bad canidates during
the node info template generation.
The Process function has been updated to separate nodes into good and
bad candidates to make the filtering match the original intent.
* add --scale-from-unschedulable flag
This change introduces a flag which will instruct the CA to ignore a
node's `.spec.unschedulable` field when creating node template for
considering which node group to scale.
Copy file name to clipboardExpand all lines: cluster-autoscaler/FAQ.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1104,6 +1104,7 @@ The following startup parameters are supported for cluster autoscaler:
1104
1104
| `scale-down-unready-enabled` | Should CA scale down unready nodes of the cluster | true |
1105
1105
| `scale-down-unready-time` | How long an unready node should be unneeded before it is eligible for scale down | 20m0s |
1106
1106
| `scale-down-utilization-threshold` | The maximum value between the sum of cpu requests and sum of memory requests of all pods running on the node divided by node's corresponding allocatable resource, below which a node can be considered for scale down | 0.5 |
1107
+
| `scale-from-unschedulable` | Should CA ignore a node's .spec.unschedulable field when creating a node template for considering to scale a node group. | false |
1107
1108
| `scale-up-from-zero` | Should CA scale up when there are 0 ready nodes. | true |
1108
1109
| `scan-interval` | How often cluster is reevaluated for scale up or down | 10s |
1109
1110
| `scheduler-config-file` | scheduler-config allows changing configuration of in-tree scheduler plugins acting on PreFilter and Filter extension points | |
Copy file name to clipboardExpand all lines: cluster-autoscaler/config/flags/flags.go
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -167,6 +167,7 @@ var (
167
167
balancingIgnoreLabelsFlag=multiStringFlag("balancing-ignore-label", "Specifies a label to ignore in addition to the basic and cloud-provider set of labels when comparing if two node groups are similar")
168
168
balancingLabelsFlag=multiStringFlag("balancing-label", "Specifies a label to use for comparing if two node groups are similar, rather than the built in heuristics. Setting this flag disables all other comparison logic, and cannot be combined with --balancing-ignore-label.")
169
169
awsUseStaticInstanceList=flag.Bool("aws-use-static-instance-list", false, "Should CA fetch instance types in runtime or use a static list. AWS only")
170
+
scaleFromUnschedulable=flag.Bool("scale-from-unschedulable", false, "Specifies that the CA should ignore a node's .spec.unschedulable field in node templates when considering to scale a node group.")
170
171
171
172
// GCE specific flags
172
173
concurrentGceRefreshes=flag.Int("gce-concurrent-refreshes", 1, "Maximum number of concurrent refreshes per cloud object type.")
0 commit comments