Is it possible to have multiple workspaces/repositories per user-code-deployment?

yes - you can have multiple repositories in a given user code deployment. When you specify the repository location, all repositories defined within the module will be pulled in.

New to Dagster, so I wonder if I am getting the terminology/concepts wrong... What I'd like to do is if I have: |-project1 |----jobs |----ops |----project1_repo.py |-project2 |----jobs |----ops |----project2_repo.py Where each project is a workspace. My understanding is that this can be achieved via the workspace.yaml like:

load_from:
  - python_file: /project1/project1_repo.py
  - python_file: /project2/project2_repo.py

What would the syntax for this look like in the user-code-deployment chart?

Have you checked out https://docs.dagster.io/concepts/repositories-workspaces/workspaces#running-your-own-grpc-server? You can point the grpc server at a particular repo file and attribute, and then specify the config in your workspace.yaml

hey @chris and @rowan gaffney, same interest here. Have you find a solution for this? I dont understand how my own grpc server helps in this context?

You can configure

dagster-user-deployments

in the helm chart directly. Each user code deployment corresponds to a grpc server that's communicating back with the dagit webserver: https://docs.dagster.io/deployment/guides/kubernetes/deploying-with-helm#deploying-dagster-on-helm check out the

dagster-user-deployments

section on the helm chart

hey @chris, thanks for the info. I am new to Dagster and love it so far. I am trying to replace our Airflow in Kubernetes. I understand the

dagster-user-deployments

but it is hard to manage multiple repositories and frequent code changes. I have to redeploy the helm chart for every repo and corresponding gRpc or I need to redeploy the user-deployment. In our use case, there are multiple users , frequently create repos, make code changes. I am trying to find a way to automatically syncronize git repos and reflect code changes.

hey baris - valid question - I'm a bit out of my depth to answer that, so going to get a team member with more experience with helm/k8s to get back to you about this

thanks @chris

Hi Baris, most users have a CICD pipeline that runs the deploy step (helm upgrade/whatever platform they’re on) on each commit

But helm deployment will have a downtime on dagit / user deployment , right?

It shouldn’t. If you just updated your user code, your dagit deployment won’t need to change at all. And the user deployment can do a rolling upgrade

what about multiple repositories? Do you recommend use same user deployment for multiple repositories or different user-deployments per github repo/branch? In our use-case there will be multiple users and multiple git repos and multiple branches. So it doesn’t look efficient to spin up a user deployment for each repo and branch. What are your recommendations?

If deploying to k8s, a user deployment is essentially 1 to 1 with whatever code you want to package in to a docker image. It’s certainly easiest to have 1 per branch