Open cnmcavoy opened 1 month ago
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.
Description
What problem are you trying to solve? Karpenter provides nodepools with a
disruption
spec to control how a nodepool can be disrupted by Karpenter to satisfy nodes.As a cluster operator, I want to be able to configure certain nodepools for only single-node consolidation (consolidation for cheaper instance types), and other nodepools for only multi-node consolidation (consolidation for larger instance sizes).
Motivation: We've found that single-node consolidation tends to lead to unnecessary or unproductive churn in large nodepools, but there are certain use-cases it is valuable for. So for most of our Karpenter nodepools, we want to be able to switch off the single-node consolidation, but leave the multi-node and emptiness consolidation in place.
How important is this feature to you?