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
Copy file name to clipboardExpand all lines: cluster-autoscaler/FAQ.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1061,7 +1061,7 @@ The following startup parameters are supported for cluster autoscaler:
1061
1061
| `max-inactivity` | Maximum time from last recorded autoscaler activity before automatic restart | 10m0s |
1062
1062
| `max-node-group-backoff-duration` | maxNodeGroupBackoffDuration is the maximum backoff duration for a NodeGroup after new nodes failed to start. | 30m0s |
1063
1063
| `max-node-provision-time` | The default maximum time CA waits for node to be provisioned - the value can be overridden per node group | 15m0s |
1064
-
| `max-node-startup-time` | The default maximum time CA waits for node to be ready from registered - the value can be overridden per node group | 15m0s |
1064
+
| `max-node-startup-time` | The default maximum time CA waits for node to be ready from registered - the value can be overridden per node group | 15m0s |
1065
1065
| `max-nodegroup-binpacking-duration` | Maximum time that will be spent in binpacking simulation for each NodeGroup. | 10s |
1066
1066
| `max-nodes-per-scaleup` | Max nodes added in a single scale-up. This is intended strictly for optimizing CA algorithm latency and not a tool to rate-limit scale-up throughput. | 1000 |
1067
1067
| `max-nodes-total` | Maximum number of nodes in all node groups. Cluster autoscaler will not grow the cluster beyond this number. | |
0 commit comments