-
Notifications
You must be signed in to change notification settings - Fork 602
🐛 Launchtemplate needs to be updated if spot options are changed #5496
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
base: main
Are you sure you want to change the base?
🐛 Launchtemplate needs to be updated if spot options are changed #5496
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-cluster-api-provider-aws-e2e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: d778b6d36ce012772b2bb23779e7a386fca21354
|
99f00ed
to
4a57ee5
Compare
New changes are detected. LGTM label has been removed. |
6f3953d
to
e0d5e11
Compare
e0d5e11
to
99c1047
Compare
/test pull-cluster-api-provider-aws-e2e |
@alexander-demicev After testing the changes in our management cluster, I needed to do more changes to make this work. PTAL, thanks. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
When the spot instances options are changed, we want to update the launch template so that the changes take effect.
Special notes for your reviewer:
I've changed the unit tests for the
LaunchTemplateNeedsUpdate
function, because some cases were passing by pure chance. Basically these security groups are always added to the incomingAWSLaunchTemplate
So if the existing
AWSLaunchTemplate
that we use in the tests don't have these security groups, the function will always return true. Tests like the one testing changes to theIamInstanceProfile
field were passing because of the different security groups, rather than the change on theIamInstanceProfile
field.Checklist:
Release note: