feat: Launch Template ASGs pin to created version #1289
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 whenasg_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. Whenasg_recreate_on_change
is false, the ASG still points to the latest (as soon as Terraform gets to it). Whenasg_recreate_on_change
is true, the older ASGs (when usingasg_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