19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Hello everyone! We have a Dagster Monorepo contain...
# deployment-kubernetesn
Nathan Skone
07/12/2023, 6:40 PMHello everyone! We have a Dagster Monorepo containing 10+ Code Locations deployed via Helm Chart to EKS. Right now we use one Helm chart, but we would like to update them independently of each other, ideally using the short git commit hash as the docker image tag to be deployed via Helm. Is anyone doing anything similar? Should we deploy independent Helm “dagster/dagster-user-deployments” charts for each of them?
Nathan Skone
07/12/2023, 6:40 PMWe already have a pipeline that builds the docker images, tags them, and pushes them to a repo, the part we are struggling with is the ideal Helm setup to handle independent deployments.
a
Adam Bloom
07/12/2023, 7:23 PMWe have multiple code locations in the same docker image, but I did peek at the helm chart real quick - I don't see why what you're describing wouldn't work. You just may need to disable automatic service account creation to avoid conflicts in running multiple user code helm charts
Adam Bloom
07/12/2023, 7:24 PMlooks like there may be some conflicts with k8s rbac for the service accounts too. https://github.com/dagster-io/dagster/blob/master/helm/dagster/charts/dagster-user-deployments/values.yaml#L144-L154
Adam Bloom
07/12/2023, 7:24 PMyou can disable both of those, handle them separately, and pass a service account name to the chart for it to use in the deployment
n
Nathan Skone
07/12/2023, 8:00 PMThank you for the advice Adam!
5 Views