The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Hi! Is it possible to set an env variable in the k8sRunLauncher? it's possible in the celeryK8sRunLauncher like this:
```...
  env:
    ENV_ONE: one
    ENV_TWO: two```


Hi <@U01REUJ8WBW>, you can specify env configmaps <https://docs.dagster.io/_apidocs/libraries/dagster-k8s#dagster_k8s.K8sRunLauncher>

Also- the env field you mention applies to celery workers, which monitor user code but don’t actually execute it. The celery-k8s launcher also takes envConfigMaps, which will apply to the k8s jobs that actually run user code.

Assuming the env is for your code (as opposed to Celery config), you’ll want to use the envConfigMaps field

One way to manage these configmaps is with our helm chart, under `extraManifests`

Hi <@U015C9U9RLK>, thanks for your quick response. So I need to pipe the values through the kubernetes environment (configmaps/secrets) for them to reach the k8sRunLauncher-created pods. I originally thought that the k8sRunLauncher could be used as the userDeployment where there is also an `env`  field