Unable to use `configured` with the celery k8s executor
See original GitHub issueWhen I try to use configured
on the celery k8s executor definition and launch a run, I get the following error:
This is because we are trying to grab the config straight from run config before processing the entire run config:
execution_run_config = run_config["execution"][CELERY_K8S_CONFIG_KEY].get("config", {})
res = process_config(execution_config_schema, execution_run_config)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
dagster - AWS credentials not found for celery-k8s deployment
The deployment configuration applies to the user code servers. Meanwhile the celery executor runs your pipeline code in separate kubernetes ...
Read more >Kubernetes Executor — Airflow Documentation - Apache Airflow
The Kubernetes executor runs each task instance in its own pod on a Kubernetes cluster. KubernetesExecutor runs as a process in the Airflow...
Read more >The Kubernetes executor for GitLab Runner
Notice: If a non-existing key will be used then job will fail on Pod creation stage. Secret volumes. Secret volume configuration instructs Kubernetes...
Read more >Use the KubernetesPodOperator | Cloud Composer
Secret variables configuration: Passes a Kubernetes Secret object to the pod. Pod affinity configuration: Limits the available nodes to schedule pods on. Full ......
Read more >Source code for dagster_celery_k8s.launcher - Dagster Docs
A run worker Kubernetes Job, which traverses the dagster run execution plan ... "Using configured with the celery-k8s executor is not supported at...
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
No, this one is pretty difficult
The refactor I mentioned is complete. Feel free to work on or assign to someone!