https://dagster.io/ logo
#deployment-kubernetes
Title
# deployment-kubernetes
i

Ignas Kizelevičius

04/26/2023, 2:20 PM
Hi, how can I change the service account of the dagster-run pod? I tried adding the following section to the helm values yaml but it dit no effect
Copy code
runLauncher:
  type: K8sRunLauncher
  config:
    k8sRunLauncher:
      runK8sConfig:
        podSpecConfig:
          serviceAccountName: dagster
a

alex

04/26/2023, 2:51 PM
This is the byproduct of some complex interactions between different ways to manage config between the user code servers and the runs that we should improve. Options to resolve: • disable
includeConfigInLaunchedRuns
assuming its safe to ignore other code server k8s settings on the run • use tags on the
@job
to provide the service account name instead https://docs.dagster.io/deployment/guides/kubernetes/customizing-your-deployment#per-job-or-per-op-kubernetes-configuration
i

Ignas Kizelevičius

04/27/2023, 6:35 AM
Thanks Alex, ill try the suggested options
@alex just to double check, currently there is not a way to set the service account via helm values? I mean, is there an issue on the dagster side regarding the launcher config or am I just doing something wrong?
the option to set tag on @job works but I would like to use helm values
I was able to set it up using the helm values, the issue was that I was adding the config on the user-code-deployment values instead of dagster deployment
a

alex

04/27/2023, 2:57 PM
interesting, the same config just in the appropriate chart? Did you have to set
includeConfigInLaunchedRuns
to false?
i

Ignas Kizelevičius

04/27/2023, 4:35 PM
Yes. No, i did not have to set that to false
4 Views