You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The EKS node pool update surge node handling logic was implemented using NASGMaxSize and NASGMaxBatchSize values only.
Describe the solution you'd like to see
We should double check the custom logic whether the newly available NASGMinInstancesInService attribute can help us replacing parts or the whole of the EKS node pool update surge node implementation logic using the built-in features of the CloudFormation template and its backing services.
Describe alternatives you've considered
If the supported max batch size and min instances in services cannot replace the custom surge logic, we can keep the current logic intact.
pregnor
changed the title
Revise EKS node pool surge node logic now that NASGMinInstancesInService is available
Revise EKS node pool surge node logic now that NASGMinInstancesInService is available in CF templates
Nov 9, 2020
Is your feature request related to a problem? Please describe.
The EKS node pool update surge node handling logic was implemented using
NASGMaxSize
andNASGMaxBatchSize
values only.Describe the solution you'd like to see
We should double check the custom logic whether the newly available
NASGMinInstancesInService
attribute can help us replacing parts or the whole of the EKS node pool update surge node implementation logic using the built-in features of the CloudFormation template and its backing services.Describe alternatives you've considered
If the supported max batch size and min instances in services cannot replace the custom surge logic, we can keep the current logic intact.
Additional context
AWS CloudFormation template UpdatePolicy attribute
The text was updated successfully, but these errors were encountered: