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

Custom Pricing Overrides for RIs, Savings Plans, and other strategies #5163

Open
jonathan-innis opened this issue Nov 25, 2023 · 1 comment
Labels
cost-optimization feature New feature or request v1.x Issues prioritized for post-1.0

Comments

@jonathan-innis
Copy link
Contributor

jonathan-innis commented Nov 25, 2023

Description

What problem are you trying to solve?

Karpenter should be able to understand custom pricing strategies by allowing users to manually override instance type/offering pricing for instance types that Karpenter chooses from. This would allow users to effectively modify the consolidation and provisioning behavior to prioritize certain instance types which they could mark as "cheaper" if they had discounts on certain instance types due to different Amazon EC2 billing strategies

How important is this feature to you?

  • 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
@jonathan-innis jonathan-innis added feature New feature or request v1.x Issues prioritized for post-1.0 cost-optimization labels Nov 25, 2023
@jonathan-innis
Copy link
Contributor Author

This is a "transferred" version of the issue in kubernetes-sigs/karpenter: kubernetes-sigs/karpenter#693

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cost-optimization feature New feature or request v1.x Issues prioritized for post-1.0
Projects
None yet
Development

No branches or pull requests

1 participant