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

Kevin

08/19/2020, 3:50 PM
Hi Dagster folk! I've been trying to upgrade my system from 0.8.5 to the latest 0.9.2, I have followed the migration guide and made the changes but my dagit image always fails with this error (attached in file). Any ideas? Any help is appreciated! I'm excited to try out the grpc for separating user code from the system code 😄
a

alex

08/19/2020, 3:52 PM
hmm its a bummer there isn’t further details but it appears that we think there is a syntax error in what you are trying to load with your
workspace.yaml
did you make any changes besides upgrading version? Are all dagster/dagit components on the same version?
k

Kevin

08/19/2020, 3:55 PM
Hi alex 🙂 all components are the latest version: 0.9.2
a

alex

08/19/2020, 3:56 PM
yea - are you certain that there are no typos or anything in any of those python files? We are getting
(SyntaxError) - SyntaxError: invalid syntax
when we try to load those files
k

Kevin

08/19/2020, 4:00 PM
mmmm okay i will take another look! thank you for the pointer alex!
thanks alex for that tip, that allowed dagit to be properly deployed!! but now I have an error with running pipelines it's compaining about invariant failed with execution for celery-k8s. however, even when i specify it in the playground config the pipeline fails to run -- all the dagster-run pods error out. any ideas? i'm updating from 0.8.5 (where i could run the same pipelines without specifying a config) to 0.9.2, and i have looked at the migration.md as well. is there something else i'm missing?
c

cat

08/19/2020, 7:09 PM
hey kevin! which invariant failed / mind sharing the stack trace?
im guessing you might be specifying the job_image in the celery_k8s executor config
which is not compatible with gprc / user code deployment (dagit expects to have to fetch the job_image from the user code deployment, instead of getting it from executor config)
k

Kevin

08/19/2020, 7:23 PM
Hi Cat! I found my issue! it was an inconsistency with my configmap-instance.yaml - i destroyed the old one when copying over the file from the latest version of 0.9.2! so now i'm going to try and figure out the ol' grpc now that i've successfully upgraded 😄
👍 1
c

cat

08/19/2020, 10:14 PM
cool, also just a heads up that the user-env configmap needs to be explicitly included in the deployment section of the values.yaml (will be fixed in 0.9.3 https://dagster.phacility.com/D4212)
🎉 1