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
However, there are cases where a very large/expensive node gets deployed to accommodate potentially many user-pods, but are kept live for just 1 user.
For example, a user has been running a "Base" profile instance, but it has been running on an r5.24xlarge. I'm not sure what conditions led to this, but the user has been alone on this expensive node for some time.
IMO we should force Karpenter to pick smaller nodes.
The text was updated successfully, but these errors were encountered:
In our
default
NodePool (everything but on-demand and GPU) Karpenter has the following matrix of options:However, there are cases where a very large/expensive node gets deployed to accommodate potentially many user-pods, but are kept live for just 1 user.
For example, a user has been running a "Base" profile instance, but it has been running on an r5.24xlarge. I'm not sure what conditions led to this, but the user has been alone on this expensive node for some time.
IMO we should force Karpenter to pick smaller nodes.
The text was updated successfully, but these errors were encountered: