The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Hi, I ran into some trouble doing a helm deploy into EKS just now. I was preparing to make and issue and submit a PR to resolve it, but wanted to ask a question first:

Is what are the differences between the `dagster-celery-k8s` and `dagster-k8s` images other than the installation of the celery packages? I havent tested a run yet, but im assuming that the celery dagit image would still work with `K8sRunLauncher` correct?

That's right - I would expect dagster-celery-k8s to work fine with a K8sRunLauncher

if you dont mind me asking, why does `dagster-k8s` exist than?  not breaking old deployments?

Why does dagster-k8s the python package exist you mean?

i had assumed that my initial helm deploy wasnt working because the chart was using the non-celery run launcher with the celery-k8s dagit image. (it was something else)

Ah, I think it would be for people who know they don't want celery and might want to use a smaller image with fewer dependencies

but it is set as the default because it works for both