feat: set min node number to 3 to avoid resume issues

When we start at 1 node, it takes time to boot other required nodes by
the autoscaler, leading to issues.
This commit is contained in:
Pierre Mavro
2021-06-22 20:59:56 +02:00
committed by Pierre Mavro
parent 4024a90295
commit be6897093e
2 changed files with 4 additions and 4 deletions

View File

@@ -202,9 +202,9 @@ impl<'a> EKS<'a> {
.map(|(instance_type, group)| (instance_type, group.collect::<Vec<_>>()))
.map(|(instance_type, nodes)| WorkerNodeDataTemplate {
instance_type: instance_type.to_string(),
desired_size: "1".to_string(),
desired_size: "3".to_string(),
max_size: nodes.len().to_string(),
min_size: "1".to_string(),
min_size: "3".to_string(),
})
.collect::<Vec<WorkerNodeDataTemplate>>();

View File

@@ -234,9 +234,9 @@ impl<'a> DOKS<'a> {
.map(|(instance_type, group)| (instance_type, group.collect::<Vec<_>>()))
.map(|(instance_type, nodes)| WorkerNodeDataTemplate {
instance_type: instance_type.to_string(),
desired_size: "1".to_string(),
desired_size: "3".to_string(),
max_size: nodes.len().to_string(),
min_size: "1".to_string(),
min_size: "3".to_string(),
})
.collect::<Vec<WorkerNodeDataTemplate>>();