-
Notifications
You must be signed in to change notification settings - Fork 378
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
Support the use of EC2 spot instances as worker nodes #228
Comments
Thanks for the feature request @cmdallas! One potential snag here is that we plan to move away from using CloudFormation under the hood in favour of managed node groups as part of #137. It seems like managed node groups don't currently support spot instances per aws/containers-roadmap#583. |
FWIW, it seems like AWS team is currently working on this feature, you can see the issue in We'll likely begin the upgrade of EKS to |
We have v1beta1 level support for EKS but it seems AWS still hasn't implemented support for spot instances in the official API aws/containers-roadmap#583 |
Sounds like AWS added spot support in aws/containers-roadmap#583 |
Seems like no API changes were required, so we should get this support without any code change. It'd be great if someone can test this so that we can close the issue. |
@muvaf can't find a way to provide SPOT capacity type similar to https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_node_group#capacity_type Looks like there is not matching field in https://doc.crds.dev/github.com/crossplane/provider-aws/eks.aws.crossplane.io/NodeGroup/v1alpha1@v0.17.0 . Am I missing something? |
@ytsarev I think you're right, seems we don't have |
Any plans to implement this? |
Fixes crossplane-contrib#228 Signed-off-by: Yury Tsarev <yury@upbound.io>
What problem are you facing?
The current worker node spec does not support the use of spot instances.
How could Crossplane help solve your problem?
Expose support for the use of EC2 spot fleets as worker nodes.
The text was updated successfully, but these errors were encountered: