IssueRaiser

[EKS] [ManagedNodeGroup]: Ability to speed up the scale down phase of Managed node update process.

<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** Opened this issue on behalf of a customer. **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?** We have quite a few large managed node groups with 100+ nodes in each and we are trying to upgrade AMI of the managed node groups. [UpdateConfig](https://docs.aws.amazon.com/eks/latest/APIReference/API_NodegroupUpdateConfig.html) seems to help with scale up phase, and the upgrade phase. However [Scale down phase](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-

Posted by nsb413 on Jan 4, 2022, 6:52 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments

reliability (Software)

[EKS] [ManagedNodeGroup]: Ability to speed up the scale down phase of Managed node update process.

nsb413Jan 4, 2022, 6:52 PM

<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** Opened this issue on behalf of a customer. **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?** We have quite a few large managed node groups with 100+ nodes in each and we are trying to upgrade AMI of the managed node groups. [UpdateConfig](https://docs.aws.amazon.com/eks/latest/APIReference/API_NodegroupUpdateConfig.html) seems to help with scale up phase, and the upgrade phase. However [Scale down phase](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-

Comments (0)

No comments yet. Start the discussion.

Comment on this issue