Hi, All. What is mean, when run is in

Started

status, but in the same time all tasks have already finished?

Hi Alexander, could you give a few more details? Is the run still stuck in

Started

?

Hi @johann I am trying to build simple pipeline with using

celery_k8s

executor. Here you can find whole project https://github.com/habibutsu/dagster-research based on minikube as playground for kubernetes. I noticed some strange thing, when I run job with configuration

ops:
  init_step:
    inputs:
      amount: 5

everything works fine, but if increase parameter

amount

to 20 or more despite all tasks complete successfully , run stay in status

started

Hi @Alexander Verbitsky, sorry just getting to this now. It looks like your helm values don’t configure the CeleryK8sRunLauncher, which is a requirement for using the

celery_k8s_job_executor

Isn't this configuration enough? https://github.com/habibutsu/dagster-research/blob/master/values/dagster.yaml#L3

Yes I think that looks good