K8SRunLauncher should allow passing arbitrary config to jobs/pods/containers
See original GitHub issueCurrently, K8SRunLauncher does not allow passing in custom config when creating Job/Pod/Container Kubernetes Object. This can cause problems when users want to pass in custom annotations[1], labels or any other config to their K8S Objects.
Ideas are being considered to implement this but needs prioritization: https://dagster.slack.com/archives/C014N0PK37E/p1597248672084000?thread_ts=1597019607.076100&cid=C014N0PK37E
[1]: sample annotation: cluster-autoscaler.kubernetes.io/safe-to-evict": "false"
https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-types-of-pods-can-prevent-ca-from-removing-a-node
This annotation can be used to stop Cluster-Auto scaler from evicting running dagster-pipeline pods.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:16
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Customizing your Kubernetes Deployment - Dagster Docs
The dagster-k8s/config tag allows users to pass custom configuration through to the Kubernetes Jobs and Pods created by Dagster during execution.
Read more >dagster/values.yaml at master - GitHub
An orchestration platform for the development, production, and observation of data assets. - dagster/values.yaml at master · dagster-io/dagster.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Additional use case from szalai1 on Slack: https://dagster.slack.com/archives/C014N0PK37E/p1597327142088800 Node-affinity to target the pipeline-runs on the nodes with GPU power.
Awesome! Glad it worked.
@szalai1 I just wanted to confirm that you were successfully able to specify node-affinities. If so, we can close this issue.