Don't provision capacity for low priority pods

[jimmyjones2]

Description

What problem are you trying to solve?

I've got a cluster running both serving and batch workloads. Some of the batch workloads are run with a very low PriorityClass which I want to consume CPU/memory on nodes that would otherwise be wasted, i.e. in the gaps left after by bin packing. Any other workloads will prempt these pods.

I can't find a way to configure Karpenter to not provision capacity for pods below a certain priority. Currently it will add capacity to run these low priority pods. Possibly when consolidating, Karpenter should ignore these pods and potentially cause them to be unschedulable.

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

[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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.