Both Azure and Google Cloud allow for an in place resizing of node groups (if it's an autoscaling node group, then you can change the min and max size of the node group). I have not found any way for eksctl to replicate this functionality, and it is quite inconvenient. For example, I have predictable spikes in usage, and I would like to change the min number of nodes in an autoscaling pool in order to anticipate these spikes in usage, so I don't have the delay of spinning up new nodes. However, I don't want to delete and recreate the node group because there will be existing pods in the old node group that cannot be migrated.
Is this a feature on the roadmap (I have not been able to find any documentation on it)? Or is there an existing workaround that isn't documented?
Both Azure and Google Cloud allow for an in place resizing of node groups (if it's an autoscaling node group, then you can change the min and max size of the node group). I have not found any way for eksctl to replicate this functionality, and it is quite inconvenient. For example, I have predictable spikes in usage, and I would like to change the min number of nodes in an autoscaling pool in order to anticipate these spikes in usage, so I don't have the delay of spinning up new nodes. However, I don't want to delete and recreate the node group because there will be existing pods in the old node group that cannot be migrated.
Is this a feature on the roadmap (I have not been able to find any documentation on it)? Or is there an existing workaround that isn't documented?