Support different consolidateAfter for different disruption reasons

[maxsxu]

Description

What problem are you trying to solve?

Allow specify different consolidateAfter for different disruption reasons.

For example:

• Disrupt after 5m if Node is Empty
• Disrupt after 1h if Node is Underutilized

Possible configurations:

apiVersion: karpenter.sh/v1
kind: NodePool
spec:
  disruption:
    strategy:
    - consolidationPolicy: WhenEmpty
      consolidateAfter: 5m
    - consolidationPolicy: WhenUnderutilized 
      consolidateAfter: 1h

How important is this feature to you?

We want to quickly scale down the empty nodes, but slowly scale down the underutilized nodes.

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