-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add per_step_k8s_config to k8s_job_executor (#25561)
## Summary & Motivation Dagster currently requires that k8s config at the op-level be defined statically with no option for configuring at launch-time (#22138). This was resolved for the celery-k8s-job-executor in #23053. This PR aims to add an identical solution to the k8s-job-executor. ## How I Tested These Changes I added a unit test in the k8s package to test that the executor per_step_k8s_config overwrites other sources (op-tag, job-tag, executor step_k8s_config). ## Changelog [dagster-k8s] Added a per_step_k8s_config configuration option to the k8s_job_executor, allowing the k8s configuration of individual steps to be configured at run launch time.
- Loading branch information
Showing
2 changed files
with
86 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters