[EKS][Feature Request]: Improved Managed Nodegroup Upgrade Experience

[awsjake]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
We are wanting a more elegant way of handling Managed Nodegroup Upgrades by specifying which nodes in the nodegroup to update in a preferred order. This is for better handling of nodegroup upgrades that fail due to pod disruption budgets (PDBs) that interfere with the nodegroup upgrades.

Which service(s) is this request for?
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
According to the documentation, the upgrade process randomly selects a node that needs to be upgraded. The preferred mechanism would enable users to prioritize the order of which nodes will be upgraded first.

Are you currently working around this issue?
We are required to use the force update option, which ignores PDBs.

How are you currently solving this problem?
We have to use the force update option or delete the pods with PDBs manually.