Consider SaaS node-based pricing in Karpenter scheduler for cost optimization

[kyontan]

Description

What problem are you trying to solve?

Currently, Karpenter's scheduler optimizes for AWS costs but does not take into account the costs of SaaS tools like Datadog or Sysdig, which often use a node-based pricing model. This can lead to scenarios where the total cost, including SaaS expenses, is higher when more nodes are utilized, even if the AWS cost alone is lower.

For example, given the same amount of resources:

• 1 Node: Higher AWS cost, but lower overall cost including SaaS expenses.
• 2 Nodes: Lower AWS cost, but higher overall cost including SaaS expenses due to node-based pricing.

This discrepancy can result in suboptimal cost efficiency and increased operational expenses for users who rely on these SaaS tools for monitoring and observability.

How important is this feature to you?

This feature is very important as it would enable more accurate cost optimization, considering both AWS and SaaS expenses. By incorporating SaaS costs into the scheduling decisions, we can achieve:

• Overall Cost Savings: More effective cost management by considering the full spectrum of operational costs.
• Resource Efficiency: Improved allocation of resources that minimizes overall expenses.
• Better Decision Making: Enhanced transparency and understanding of the cost trade-offs involved in different scheduling decisions.

---

• 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

[jmdeal]

Closing as a duplicate of #5033.