Karpenter is not functioning as expected when used with reserved instances

[paramjeet01]

Description

Observed Behavior:
When a node pool with reserved capacity and a public pool are present, Karpenter does not prioritize utilizing the reserved capacity.

Expected Behavior:
Karpenter should prioritize using the reserved capacity

Reproduction Steps (Please include YAML):

• Create a nodepool with multiple instance types.
• Create a capacity reservation with one specific instance type
• Scale up the service deployment.

Versions:

• Chart Version: 1.05
• Kubernetes Version (kubectl version): 1.31

• 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.

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.

[enxebre]

Reserved instances support seems WIP at the moment
#1911
#1760