tm-nadavsh
tm-nadavsh
@engedaam sure i will share them, but as far as i know one nodepool should not impact a different nodepool no matter the configuration, am i wrong? nodepools: ``` apiVersion:...
same issue here
@nohant FYI > sadly i noticed its the standard way of working for karpenter. im always with the biggest node possible from AWS. > > ``` > spec: > expireAfter:...
@nohant what version of karpenter are you running, if its the latest(0.37.0) it seems like you have multiple misconfigurations, `expireAfter: 1h` should be inside spec.disruption WhenEmptyOrUnderutilized, not a real value,...
@igorbdl As far as i understand, it does not matter if spot to spot consolidation is enabled regarding this issue, the issue is that karpenter does not scale down nodes...