Hello! Upgrading out helm release of `dagster/dags...
# deployment-kubernetes
j
Hello! Upgrading out helm release of
dagster/dagster
from
0.13.16
to
0.14.6
and am getting this error
Copy code
│ Error: release dagster failed, and has been rolled back due to atomic being set: cannot patch "dagster-daemon" with kind Deployment: Deployment.apps "dagster-daemon" is invalid: spec.template.spec.containers[0].livenessProbe: Required value: must specify a handler type
Noticed this as part of the
0.14.0
changelog
• [Helm] The default liveness and startup probes for Dagit and user deployments have been replaced with readiness probes. The liveness and startup probe for the Daemon has been removed. We observed and heard from users that under load, Dagit could fail the liveness probe which would result in the pod restarting. With the new readiness probe, the pod will not restart but will stop serving new traffic until it recovers. If you experience issues with any of the probe changes, you can revert to the old behavior by specifying liveness and startup probes in your Helm values (and reach out via an issue or Slack).
Wondering if we have to specify the liveness and startup probes or if theres another workaround to get this up
r
If you just remove the liveness/startup probes from your values.yaml, you should be able to get up and running. https://artifacthub.io/packages/helm/dagster/dagster?modal=values&path=dagit.livenessProbe has this empty - but if you’re overriding this, you might encounter some errors.
j
not for dagit but for the daemon
r
same thing applies i believe
👍 1
j
that worked, thanks Rex!
103 Views