Heya. I tried installing Dagster via the Helm chart on latest

master

, it's resulting in a CrashLoopBackoff in

dagster-dagit

and

dagster-daemon

on this log:

Error 1: Received unexpected config entry "params" at path root:postgres_db. Expected: "{ db_name: (String | { env: String }) hostname: (String | { env: String }) password: (String | { env: String }) port?: (Int | { env: String }) username: (String | { env: String }) }

Looks like it isn't expecting

params

in the `ConfigMap`:

config:
    postgres_db:
      username: test
      password:
        env: DAGSTER_PG_PASSWORD
      hostname: dagster-postgresql
      db_name:  test
      port: 5432
      params: 
        {}

(occurs in multiple sections in the default

dagster.yaml

)

What version of dagster are you using?

helm -n dagster install dagster dagster-0.11.3.tgz -f dagster-values.yaml

where

dagster-0.11.3.tgz

is from:

helm package helm/dagster

in latest

master

Ah let me clarify - what version of dagster are you using in the images in the chart?

I'm not overriding the image tag, so it's getting the default from the Helm chart, which looks like 0.11.3.

helm -n dagster list
NAME   	NAMESPACE	REVISION	UPDATED                             	STATUS  	CHART         	APP VERSION
dagster	dagster  	1       	2021-06-15 13:07:55.068108 -0400 EDT	deployed	dagster-0.11.3	0.11.3

and the container is:

<http://docker.io/dagster/dagster-celery-k8s:0.11.3|docker.io/dagster/dagster-celery-k8s:0.11.3>

Yeah- these app version/chart version are correct in the packaged versions of the chart (in the remote helm repository), but not on master. We can change the version to “dev” on master to make this explicit

Setting

dagit.image.tag

and

dagsterDaemon.image.tag

to

0.11.13

works with the chart on master, no more CrashLoopBackoff 👍