Price delta threshold

[Rylon]

Description

Description

What problem are you trying to solve?

We've noticed Karpenter can spend a lot of time needlessly disrupting nodes to replace them essentially the same exact set of nodes, which causes a lot of churn, and at time, issues with rate limiting. It would be helpful if we could configure a nodepool so there was a price delta threshold, which Karpenter would consider before deciding to disrupt a node, for example maybe the cost savings need to be above a certain percentage for it to be worth all the disruption?

How important is this feature to you?

We find Karpenter to be quite disruptive at times, as it can get into a loop where it seems to be constantly replacing nodes with the same types, or so close that it doesn't matter, and it can be quite disruptive to deployments as they end up being evicted and stuck pending mid-deploy. We want to be able to tell Karpenter to be a little bit less aggressive when it comes to finding the cost savings?

• 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

[k8s-ci-robot]

This issue is currently awaiting triage.

If Karpenter contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Rylon]

Re-opened here from aws/karpenter-provider-aws#8784 (comment)