Configuring SpotToSpotConsolidation per Nodepool #1449
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Description
What problem are you trying to solve?
We want to enable SpotToSpotConsolidation for certain clusters, but currently, it's a global setting that applies to all nodepools. This restriction forces us to keep the setting turned off, as some nodepools prefer to allow disruptions for cost savings.
How important is this feature to you?
Our expiration time for nodepools is 1-10 days. If expensive EC2 instances are launched by Karpenter, it takes a while to replace them with cheaper ones. It would be great to make it configurable per nodepool as it would allow us to optimize cost savings while maintaining desired configurations for specific nodepools.
The text was updated successfully, but these errors were encountered: