Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Launch Template ASGs pin to created version #1289

Conversation

lowjoel
Copy link

@lowjoel lowjoel commented Mar 31, 2021

PR o'clock

Description

When creating worker node groups with Launch Templates, the created ASGs currently use $Latest as the version of the Launch Template to start nodes with. When asg_recreate_on_change is false, that's expected, but when asg_recreate_on_change is true, this means that as soon as a new Launch Template is created the old ASGs will start using the new launch template.

This changes the logic to support a $Created value, which would then reference the version created in Terraform. When asg_recreate_on_change is false, the ASG still points to the latest (as soon as Terraform gets to it). When asg_recreate_on_change is true, the older ASGs (when using asg_recreate_on_change would still reference the older LT version, and so compute capacity won't be lost should the new LT have problems spinning up nodes.

Checklist

@lowjoel lowjoel changed the title enhancement: Launch Template ASGs pin to created version feat: Launch Template ASGs pin to created version Mar 31, 2021
@lowjoel
Copy link
Author

lowjoel commented Mar 31, 2021

Not sure why docs are failing - let me know if something requires fixing.

@lowjoel lowjoel force-pushed the create-launch-template-pin-version branch from 5cf93c9 to 3c05fba Compare April 30, 2021 07:17
@lowjoel
Copy link
Author

lowjoel commented May 16, 2021

Hey @barryib @james-callahan - anything I need to do to get a review on this please?

@barryib
Copy link
Member

barryib commented May 19, 2021

@lowjoel I think this will be solved in #1370. What do you think ?

@lowjoel
Copy link
Author

lowjoel commented May 19, 2021

Yeah I think that could work too. It implements the same thing in a different way. If that gets merged I think this one can be closed.

@barryib
Copy link
Member

barryib commented May 19, 2021

Yeah I think that could work too. It implements the same thing in a different way. If that gets merged I think this one can be closed.

Great. So let close this one. Thanks again for your help.

@barryib barryib closed this May 19, 2021
@barryib
Copy link
Member

barryib commented May 19, 2021

It's now implemented in #1370

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants