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.

Sign up for GitHub

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

Jump to bottom

How is the load distributed in the following three instances? Which type of instance would be prioritized for use? #7573

Open
txjjjjj opened this issue Jan 8, 2025 · 1 comment
Open

How is the load distributed in the following three instances? Which type of instance would be prioritized for use? #7573

txjjjjj opened this issue Jan 8, 2025 · 1 comment
Labels
documentation Improvements or additions to documentation triage/solved Mark the issue as solved by a Karpenter maintainer. This gives time for the issue author to confirm.

Comments

@txjjjjj
Copy link

txjjjjj commented Jan 8, 2025

Description

How is the load distributed in the following three instances? Which type of instance would be prioritized for use?

Premise: The pod's requested resources can be fulfilled by all three instances.

      - key: node.kubernetes.io/instance-type
        operator: In
        values:
        - c7i-flex.xlarge
        - c7i.large
        - c7gd.2xlarge
@txjjjjj txjjjjj added bug Something isn't working needs-triage Issues that need to be triaged labels Jan 8, 2025
@jmdeal jmdeal added documentation Improvements or additions to documentation triage/solved Mark the issue as solved by a Karpenter maintainer. This gives time for the issue author to confirm. and removed bug Something isn't working needs-triage Issues that need to be triaged labels Jan 10, 2025
@jmdeal
Copy link
Contributor

jmdeal commented Jan 10, 2025

It depends if Karpenter is launching a spot or an on-demand instance. If it's on-demand, the cheapest compatible instance type will be used. With spot, the PCO strategy is used, which makes a compromise between price and availability to reduce interruptions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation triage/solved Mark the issue as solved by a Karpenter maintainer. This gives time for the issue author to confirm.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jmdeal @txjjjjj