You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently facing a following issue: the cluster is optimized for its size, so no consolidation is happening. We launch a new CI job which triggers a spawining of a new node, as soon as the job is finished karpenter removes the node which means that we will need to wait for a new node to come up, pull the image, etc increasing the overall wait time.
Previously this could have been fixed by using ttlSecondsAfterEmpty but as far as I can see, there is no such option anymore. Not sure if #735 covers the issue (it less about the consolidation and more about the removal of an empty node).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
We are currently facing a following issue: the cluster is optimized for its size, so no consolidation is happening. We launch a new CI job which triggers a spawining of a new node, as soon as the job is finished karpenter removes the node which means that we will need to wait for a new node to come up, pull the image, etc increasing the overall wait time.
Previously this could have been fixed by using
ttlSecondsAfterEmpty
but as far as I can see, there is no such option anymore. Not sure if #735 covers the issue (it less about the consolidation and more about the removal of an empty node).My nodepool config:
Sadly
consolidateAfter
doesnt work withconsolidationPolicy: WhenUnderutilized
. Any suggestions?Beta Was this translation helpful? Give feedback.
All reactions