Feature request: Update upgrade execution logic

[bryantbiggs]

Use case

The process for updating an EKS managed nodegroup is defined here https://docs.aws.amazon.com/eks/latest/userguide/managed-node-update-behavior.html

In addition, there are 4 upgrade scenarios for the compute constructs available within a data plane:

1. Update Fargate profiles via replacement once the control plane has been updated (eksupgrade calls the eviction API on behalf of the user requesting the upgrade)
2. DONE: fix: Modify workflow to use new eks models - Release 0.7.0 #78 - 0.7.0 Update EKS managed nodegroups using the built-in functionality and controlled via the update config (eksupgrade simply updates the nodegroup to the desired settings and EKS managed nodegroup handles the update process)
3. Update self-managed nodegroups using the graceful termination of the node-termination-handler in coordination with the instance refresh functionality of an autoscaling group. This process should be used if the node-termination-handler is deployed within the cluster, the autoscaling group is monitored by the NTH for lifecycle events, and an instance refresh configuration is present on the launch template used by the autoscaling group
4. Update self-managed nodegroups using logic similar to that of the EKS managed node group (like this)

Solution/User Experience

Users simply use the logic provided by eksupgrade to gracefully update their data plane compute while avoiding disruptions and/or downtime

Alternative solutions

None

[github-actions]

This issue has not received any attention in 30 days. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.