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
dagster-run coordinator pods don't like to be rescheduled, and sometimes in Kubernetes clusters, cluster-autoscaler reclaims nodes killing the pods running in them. To avoid this issue it's enough to add a PodDisruptionBudget to the dagster helm chart:
It would be nice if the run coordinators were resilient to these kind of events, but this at least solves the cluster-autoscaler problem, so I thought I would share it here.
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
-
dagster-run coordinator pods don't like to be rescheduled, and sometimes in Kubernetes clusters, cluster-autoscaler reclaims nodes killing the pods running in them. To avoid this issue it's enough to add a
PodDisruptionBudget
to the dagster helm chart:It would be nice if the run coordinators were resilient to these kind of events, but this at least solves the cluster-autoscaler problem, so I thought I would share it here.
Beta Was this translation helpful? Give feedback.
All reactions