Hi folks, has anyone managed to run celery-k8s against a different cluster? I’ve been unable to make either of these options stop dagster from launching runs in cluster:

execution:
  celery-k8s:
    config:
      load_incluster_config: False
      kubeconfig_file: "/conf.yaml"

(On dagster 0.12.5)

Hi Alex - I think in this case that parameter affects the pods for the ops, but not for the run worker itself. Those parameters are actually available as config on the run launcher which I think would do what you want, but it looks like the flag to set it is available on the helm chart for the K8sRunLauncher but not the CeleryK8sRunLauncher: https://github.com/dagster-io/dagster/blob/master/helm/dagster/schema/schema/charts/dagster/subschema/run_launcher.py#L28-L66 We can add those flags but it would probably require an upgrade. If you have the ability to edit your local copy of the helm chart templates, I think it would be as simple as adding those same values

load_incluster_config: false
kubeconfig_file: "/conf.yaml"

to the config that's set here: https://github.com/dagster-io/dagster/blob/master/helm/dagster/templates/helpers/instance/_run-launcher.tpl#L5

awesome thanks so much @daniel, i’ll do a bit of digging here