Polys
06/30/2021, 7:36 AMimagePullSecrets
for the k8sRunLauncher
?
We are in a situation where:
• everything works ok when a dagster-run-...
pod happens to get scheduled on the same node as dagster-user-deployment-...
because the image is cached, but
• fails to pull the image on nodes that don't have it already because it's missing pull secrets.
Many thanks in advance :)daniel
06/30/2021, 2:14 PMimage_pull_secrets
key that you can set in your dagster.yaml, for example:
run_launcher:
module: dagster_k8s.launcher
class: K8sRunLauncher
config:
image_pull_secrets:
- name: your_secret_here
- name: your_other_secret_here
Polys
06/30/2021, 2:48 PMrunLauncher:
config:
k8sRunLauncher:
envSecrets:
- name: ...
envConfigMaps:
- name: ...
runLauncher:
config:
k8sRunLauncher:
envSecrets:
- name: ...
envConfigMaps:
- name: ...
imagePullSecrets:
- name: ...
daniel
06/30/2021, 2:54 PMimagePullSecrets:
- name: your_secret_here
(separate from the runLauncher key - that will then result in your dagster.yaml being set up in the format of my original answer. Forgot you would be using the Helm chart)Polys
06/30/2021, 5:13 PM