https://dagster.io/ logo
Powered by
#dagster-kubernetes
Title
# dagster-kubernetes
k

Kirk Stennett

10/08/2021, 4:39 PM
Hey all, I'm having a problem trying to set helm values for the dagster user code deployment. I can't seem to override the tags on each of the deployments that I have. I've tried running all variations of:
Copy code
noglob helm install --set deployments[0].image.tag=gh.57,deployments[1].image.tag=gh.57 dagster-code . -ngh-57
and no luck, that includes multiple set commands, set-string, also including my values.yaml and so on. Any idea why that might not work and is this something with my dagster configuration or just helm? No matter what the deployment always has the tag 
v0.13.0
, included my values yaml reference.
r

rex

10/08/2021, 4:43 PM
your top level key looks off. All this should be nested under 
dagster-user-deployments:
k

Kirk Stennett

10/08/2021, 4:44 PM
Interesting, helm didn't complain about that, but I'm also running off of the set from 0.11.3 and running dagster 0.11.13. Would setting the version flag prevent this? Is it just trying to reconcile against the most recent chart version?
r

rex

10/08/2021, 4:44 PM
which helm chart are you using? The standalone 
dagster-user-deployments
chart or the full 
dagster
chart?
k

Kirk Stennett

10/08/2021, 4:49 PM
The standalone chart
Though admittedly, I am not sure if I copied it out of the dagster chart or not
When I apply with the values yaml it overrides the tags and everything properly. Mine mimics this: https://github.com/dagster-io/dagster/blob/master/helm/dagster/charts/dagster-user-deployments/values.yaml
r

rex

10/08/2021, 5:01 PM
When I apply with the values yaml it overrides the tags and everything properly.
What applies properly? Your custom deployments and tags, or just the chart with default helm values?
You should try running
Copy code
noglob helm install --set dagster-user-deployments.deployments[0].image.tag=gh.57,dagster-user-deployments.deployments[1].image.tag=gh.57 dagster-code . -ngh-57
k

Kirk Stennett

10/08/2021, 5:12 PM
Didn't work, I also tried manually setting every value I need in case it wasn't working from the fields being required
And when I run 
helm upgrade dagster-code . -f values.yaml -n gh-57
it applies the values from that yaml properly
looks like my values.yaml is automatically getting applied. I think this is something around the directory. I have a file structure like: 
Chart.yaml, charts->user-deployments->values.yaml
, so not everything is top level in this directory. when I renamed the values yaml it threw an error saying:
Copy code
Error: values don't meet the specifications of the schema(s) in the following chart(s):
user-deployments:
- (root): deployments is required
even though I'm using a set command that sets each of those fields
All right I figured it out: Apparently I had this set up so that it was using the dagster chart and calling the user deployments as a sub-chart. In doing so, it referenced the 
values.yaml
in that directory for all it's config and because it was a subchart it ignored my "top level" set commands. When I started running all of this from the user deployments directory it started working properly. I just need to update everything on my end to support this now. Thanks @rex
Powered by