Feature request: Support updating Fargate profiles

[bryantbiggs]

Use case

Fargate profiles use a node based off the Kubernetes version of the control plane at the time of the node creation. Once the control plane has been upgraded, the Fargate profiles will not be updated until they have been "rolled" (remove and replace with new nodes that will use a version that matches the control plane). The safest way to do this is to simply use the Kubernetes eviction API once the control plane has been updated

Solution/User Experience

When users use eksupgrade, any Fargate profiles should also be updated gracefully as well. Fargate profile nodes are identified by their node name that is prefixed with fargate- such as fargate-ip-10-0-14-253.ec2.internal

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.