FYI, for anyone who has this issue - looks like th...
# ask-community
a
FYI, for anyone who has this issue - looks like this commit broke our helm upgrade - https://github.com/dagster-io/dagster/commit/d247ff871b720d95383457d5a9d52f5bc29af94e
Copy code
Error: UPGRADE FAILED: template: dagster-user-deployments/templates/deployment-user.yaml:99:20: executing "dagster-user-deployments/templates/deployment-user.yaml" at <ne $deployment.readinessProbe.enabled false>: error calling ne: incompatible types for comparison
We were using basically all default values in our yaml, nothing fancy etc - addressed it by adding enabled to the
readinessProbe
attribute explicitly in our
values.yaml
file. I assume this is since the values.yaml file had no default
enabled
attribute you should check to see if it's set or not first? I can try and put up a quick PR to fix this if it's the way to go Dagster team if you agree, and it doesn't create too much more work for you.
(I guess
helm repo upgrade
, plus a
helm show values
will also do the trick and show you "what you need to fix") so maybe a PR is not essential.