Skip to content
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

[EKS] [request]: Support Instance Market Options of Spot instances for managed node groups #1575

Open
0xlen opened this issue Nov 25, 2021 · 3 comments
Labels
EKS Managed Nodes EKS Managed Nodes EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue

Comments

@0xlen
Copy link

0xlen commented Nov 25, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
Managed node group can support spot instance market option for setting max price.

Which service(s) is this request for?
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
As EKS managed node groups supports Spot instance feature, by default it is using optimal Spot max price to ensure capacity provisioning and bid with low cost. But I am wondering if I can define lower Spot max price in managed node group or my launch template, which can offer cost-effective option to run flexible jobs (e.g. batch processing) that can start/stop anytime.

However, right now, it is not supported and the selection can be blocked with following message if choose launch template that defined maximum price when creating managed node group:

Instance market options (EC2 Spot) are not supported in launch templates used with Managed Node Groups.

Screenshot 2021-11-25 at 14 54 33

Are you currently working around this issue?
Using self-managed node group

Attachments

(In the advanced detail of the launch template can define maximum price)
image

@0xlen 0xlen added the Proposed Community submitted issue label Nov 25, 2021
@mikestef9 mikestef9 added EKS Amazon Elastic Kubernetes Service EKS Managed Nodes EKS Managed Nodes labels Nov 25, 2021
@sergeyshevch
Copy link

Or also as a great alternative will be to add ability of allocation strategy configuration on underlying ASG

@lwille
Copy link

lwille commented Jan 18, 2024

Is there any other place where once we see the status of this? Or is it just abandoned?

@DaazKu
Copy link

DaazKu commented Mar 7, 2024

Example use case

It is recommended to use alternative instance types when using spot instances. Source https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html
image

In our case we use c6i.2xlarge instances.

So to have similar or better performances we can define this:

      capacity_type = "SPOT"
      instance_types = [
        "c6i.2xlarge",
        "c6in.2xlarge",
        "c7i.2xlarge",
      ]

On-Demand Price for US east at the moment:

  • c6i.2xlarge -> $0.34
  • c6in.2xlarge -> $0.4536
  • c7i.2xlarge -> $0.357

Without being able to set max price, we can end up paying more than on-demand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EKS Managed Nodes EKS Managed Nodes EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue
Projects
None yet
Development

No branches or pull requests

5 participants