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
Actually, my question or issue is that when the load on any node is reduced e.g only one pod running on a node that was provisioned by karpenter previously , is not getting evicted as it is underutilized as only one pod is running on it
so is there any mechanism that moves that pod to another node (which has a capacity) and deleted the new node ?
in simple terms Reallocating the pods in nodes for better resource utilization
i hope made my point clear , let me know if there is any ambiguity
The text was updated successfully, but these errors were encountered:
Hello @hjavaid06 ,
Today, Karpenter does not have the capability to evict nodes which are lightly utilized. Though we do have plan to implement a similar feature #1091.
With that being said, you can set the ttlsecondsuntilexpired value in the Karpenter Provisioner Spec to have Karpenter refresh nodes periodically. Just be sure you have Pod Disruption Budgets in place for your critical workloads given Karpenter does not limit the number of concurrent node refresh actions at this time.
Is an existing page relevant?
yes
What karpenter features are relevant?
Deprovisioning
Actually, my question or issue is that when the load on any node is reduced e.g only one pod running on a node that was provisioned by karpenter previously , is not getting evicted as it is underutilized as only one pod is running on it
so is there any mechanism that moves that pod to another node (which has a capacity) and deleted the new node ?
in simple terms Reallocating the pods in nodes for better resource utilization
i hope made my point clear , let me know if there is any ambiguity
The text was updated successfully, but these errors were encountered: