Joël Luijmes
12/17/2020, 2:42 PMKubernetesRun
but these are only strings. Is there currently an easy way to provide secrets as envs?
My intuition says I have to provide a custom job yaml then, is that correct, or am I missing an easier way?Jim Crist-Harif
12/17/2020, 2:45 PMKubernetesRun
, or on the agent as the default job yaml (with --job-template
).Jim Crist-Harif
12/17/2020, 2:47 PMScott Zelenka
12/17/2020, 3:22 PM--job-template
just to define them.Jim Crist-Harif
12/17/2020, 3:28 PMbut it allows you to skip the two-step process of using theOh neat. Note that for simple environment variables (not secrets) you can use thejust to define them.--job-template
--env
cli flag instead if you're setting them at the agent level - no need to add a custom job template just for environment variables.Joël Luijmes
12/17/2020, 3:33 PMJim Crist-Harif
12/17/2020, 3:37 PMJim Crist-Harif
12/17/2020, 3:38 PMPedro Martins
12/17/2020, 4:00 PMNuno Silva
12/17/2020, 4:01 PMimage_pull_secret
in DaskKubernetesEnvironment
and it would work. also I'd add image_pull_secret
in kubernetes agent. Now like @Pedro Martins I add it in KubernetesRun but it doesn't work. So now the only way is through job_template?Jim Crist-Harif
12/17/2020, 4:13 PMKubernetesRun
object or on the agent (note that the Secret
itself needs to already exist in the namespace). You do need to ensure that the version of the k8s agent you're running is up to date, or that feature will be ignored. If this is not working for you, this is a separate issue than Joel's above - please open a new thread.Joël Luijmes
12/17/2020, 5:02 PM