@esspee, I’m reposting this here, since I think it is the right place.
10/04/2022, 9:03 PM
Hey @esspee, sorry, missed your message. lakeFS on GCS requires a postgresql database. Do you have one in place?
If you deploy lakeFS with the Helm chart, it should spin up postgres in a container so you can easily get started (not suitable for production)
10/04/2022, 9:51 PM
Thanks. I’ve used the helm charts and I get the above error. Should the lakeconfig element be added to the values.yaml? If yes then a lot of the postgres config is skipped in the deployment. yaml. This is the confusing part
10/04/2022, 9:54 PM
Are you using a custom values file? If so, can you please share it?
10/05/2022, 5:56 AM
No basically I’ve just added the lakeconfig properties into the values. Yaml. By doing this it seems also of Postgres config is not run. So that’s the confusion. Should the lakeconfig properties be added to values. yaml?
10/05/2022, 6:04 AM
@esspee, can you please share the final values.yaml file you're using? (Make sure to omit any sensitive information)
Specifically, note that the postgres connection string should be specified separately from the lakefsConfig property. The reason for this is that it is sensitive. From the docs:
secrets:# replace DATABASE_CONNECTION_STRING with the connection string of the database you created in a previous step.# e.g.: <postgres://postgres:myPassword@localhost/postgres:5432|postgres://postgres:myPassword@localhost/postgres:5432>databaseConnectionString:[DATABASE_CONNECTION_STRING]# replace this with a randomly-generated stringauthEncryptSecretKey:[ENCRYPTION_SECRET_KEY]lakefsConfig:|blockstore:type:gs# Uncomment the following lines to give lakeFS access to your buckets using a service account:# gs:# credentials_json: [YOUR SERVICE ACCOUNT JSON STRING]
@esspee, thank you. Since you're using "localhost" as the database host, I'm assuming you expect lakeFS to spin a database in a container for you - for learning purposes. Am I right in assuming that?