-
Notifications
You must be signed in to change notification settings - Fork 628
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
Fallback instance type #569
Comments
Yes, we had the same issue and our idea was to do the same. Is someone already working on it? |
Here is a WIP for this idea - Kostiantyn-Vorobiov#1 (haven't tested in the real environment) |
I really like the idea. I don't think the implementation will work because we use EC2 Launch Templates. As far as I know the Launch Templates options and the instance type options do not mix in the So instead of changing the instance type, we could create a second Launch Template in Terraform and change the
@npalm how does this sound to you? |
According to the documentation - Also, there is a more robust solution with spot fleet requests. But that requires a lot of changes. |
In that case overwriting should be the way forward link to docs: https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RunInstances.html |
@Kostiantyn-Vorobiov feel free to open a draft (WIP) PR |
This should be resolved by #898 |
Fallback is available |
A feature request: The possibility to specify secondary instance type in case of "There is no Spot capacity available that matches your request", code: 'InsufficientInstanceCapacity' error.
I think we could have a fallback launch template with another instance type or overwrite
InstanceType
in the current launch template in case if AWS answers with 'InsufficientInstanceCapacity' error.The text was updated successfully, but these errors were encountered: