-
-
Notifications
You must be signed in to change notification settings - Fork 319
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
Recent instance types (T3, R5, etc.) are not supported #294
Recent instance types (T3, R5, etc.) are not supported #294
Comments
@bilalmughal thanks for the heads-up, I'll create a new build containing the updated instance type information. |
@bilalmughal please give #308 a try, this should add support for all recent instance types. I think as of now we need to manually blacklist the ARM instance types, before we have a way to distinguish them by some attributes. |
@cristim I can not give it a try as of now. I am on stable build in production and can not do it now. |
@bilalmughal feel free to take your time, but I'll only merge this once myself or someone else manages to test it and can confirm it works as expected. |
* Update dependencies, including instance type data Fixes #294. * Rename repo to AutoSpotting/AutoSpotting * Add a new coveralls token
Github issue
Build number
Configuration
Summary
AutoSpotting lacks support for the recent instance types, because we lack spec and/or pricing information for them, which should come from the upstream ec2instances.info instance type database.
Steps to reproduce
and also
Expected results
For both these cases the groups should be replaced by T3 spot instances.
Actual results
The groups keep running their on-demand nodes, AutoSpotting fails to launch any spot nodes for them.
The text was updated successfully, but these errors were encountered: