Hi All, I ran some pipelines on dagster --> the pipeline spins up a new node under a specific k8s node-pool and after the job finished it seems that the node still running and didn’t terminate although the job finished. Do you know what can be the issue in dagster?

There is a certain delay before an inactive node is turned off. On which cloud provider are you?

GCP

yeah scaling down takes a couple of minutes then. This has nothing to do with dagster though, but rather k8s configuration