-
Notifications
You must be signed in to change notification settings - Fork 170
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 #693
Comments
This seems like a stopgap at best. I would posit that cloud providers should be responsible for understanding pricing on behalf of their customers, and not require their customers to configure things that should already be known. Further, even if we did introduce this, I'm not sure about introducing this in karpenter-core -- it may be better suited as a provider specific feature. |
Agreed, I don't think that this should have been transferred. Unfortunately, now that it is transferred and we are in a different organization now, we just have to re-create the original issue in |
There is another use-case for this which is not provider-specific. Datadog charges us $21 per host per month. If 2 nodes have the same per-core price on EC2, the largest one will turn out to be cheaper:
Karpenter makes us spend 14% more by not consolidating towards larger same-price instances. Pricing overrides could be used for this purpose, by adding $X to every instance price, but it could also be a first-class concept. |
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?
The text was updated successfully, but these errors were encountered: