19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
announcements
dagster-airbyte
dagster-airflow
dagster-bigquery
dagster-cloud
dagster-cube
dagster-dask
dagster-dbt
dagster-de
dagster-ecs
dagster-feedback
dagster-kubernetes
dagster-machine-learning
dagster-noteable
dagster-releases
dagster-serverless
dagster-showcase
dagster-snowflake
dagster-spatial
dagster-support
dagster-wandb
dagstereo
data-platform-design
events
faq-read-me-before-posting
gigs-freelance
github-discussions
introductions
jobs
random
tools
豆瓣酱帮
Title
m
Mykola Palamarchuk
02/02/2022, 9:39 PMAnd another relative question: is it possible to run some jobs with Celery but others with K8s executor in the context of the same Dagster instance?
o
owen
02/02/2022, 10:13 PMHi @Mykola Palamarchuk! Each job can independently specify its executor_def argument: https://docs.dagster.io/deployment/executors#overview
sadly, while my note above is true in general, it turns out that this isn't the case for the celery k8s executor (which is special in that it requires that you have a specific run launcher on the instance) cc @daniel
m
Mykola Palamarchuk
02/03/2022, 7:28 AMI'm asking about that especially because Helm chart has only one
runLauncher.typed
daniel
02/03/2022, 12:57 PMCurrently the instance can only have a single run launcher. We’d like to make it in the future so that you can choose whether to use celery or not without needing to swap out the run launcher though.