-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Spotinst: Selecting a default Instance Group in Spot Ocean should be optional #9699
Conversation
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liranp, rdrgmnzs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
} | ||
} | ||
|
||
klog.V(4).Infof("Detected default launch spec: %q", b.AutoscalingGroupName(ig)) | ||
} | ||
|
||
// Rename the instance group to avoid duplicate tasks with same name. | ||
ig.Name = fi.StringValue(ocean.Name) |
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.
HEy @liranp !
Could it be that this line introduced a bug I might be facing?
By overriding ig.Name it messes up userdata for default nodes:
ocean.UserData, err = b.BootstrapScriptBuilder.ResourceNodeUp(c, ig)
Because now nodeUp tries to fetch instance group config with name "ocean.Name" which ofcourse it doesn;t exist
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.
This PR changes the way the default Instance Group for Spot Ocean is selected to allow users to create new clusters with multiple Instance Groups (#9471) without having to generate their manifests first to select the default by adding the metadata label (
spotinst.io/ocean-default-launchspec
).