19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Hi, when using values.yaml for a Helm-k8 postgres ...
# announcementsp
Peter B
04/14/2021, 11:41 PMHi, when using values.yaml for a Helm-k8 postgres implementation, and filling out the values (per a prior post's values.yaml above) , am receiving the below errors for Dagit+Daemon:
1. psycopg2.errors.InvalidSchemaName: no schema has been selected to create in
LINE 2: CREATE TABLE secondary_indexes (
--> however there is no option to specify a schema in values.yaml. Also, there doesn't seem to be an option for the Helm values.yaml implementation to specify a connection string instead, where a schema search path could be used
2. Receiving 'dagster.core.errors.DagsterInstanceMigrationRequired: Instance is out of date and must be migrated (Postgres run storage requires migration). Database is at revision None, head is 7cba9eeaaf1d. Please run `dagster instance migrate`'.
Does anyone know how these could be fixed? Really appreciate your help, thanks.
(Edit: The pods are on crash loop so can't run 'dagster instance migrate')
r
rex
04/14/2021, 11:49 PMhey - have you tried our migration guide? https://docs.dagster.io/deployment/guides/kubernetes/how-to-migrate-your-instance
rex
04/14/2021, 11:49 PMthis will run a kubernetes job that will run the migration for you, since the pods are down
rex
04/14/2021, 11:50 PMfor any other Helm/Kubernetes questions, please post on #dagster-kubernetes
p
Peter B
04/15/2021, 12:32 AMExcellent, ok will do, thank you
Peter B
04/15/2021, 12:33 AMI haven't tried the migration guide, as this is my initial setup
Peter B
04/15/2021, 12:33 AMBasically, I suspect it is picking up a single table in the 'public' schema of the database that doesn't fit the expected data model.
Peter B
04/15/2021, 12:34 AMbut, we don't want to put it in the public schema, and values.yaml doesn't include an option for a schema, or appear to include the option for specifying a PG connection string
Peter B
04/15/2021, 12:34 AMtherefore, we are unable to push it to where we need to, is this understanding correct? Thanks
Peter B
04/15/2021, 12:36 AMPlus- the migrate may destroy our data that's in the public schema.
r
rex
04/15/2021, 12:40 AMcc @prha should alembic be running into these problems if tables are created in a db with existing tables?
p
Peter B
04/15/2021, 12:44 AM(hoping to specify schema)
Peter B
04/15/2021, 12:44 AMthanks
p
prha
04/15/2021, 1:00 AMI see… I think we’ll have to change our helm chart to alternatively take in a connection string as a value
p
Peter B
04/15/2021, 1:03 AMprha, that would be super helpful. The reason for this is that for example, with the connection string, it allows us to do 2 things :
1. Add ssl-verify=full
2. Add a custom schema search-path to the string
?options=--search_path%3d<my-schema>
4 Views