Title
#help
Iddo Avneri

Iddo Avneri

10/04/2022, 6:53 PM
@esspee, I’m reposting this here, since I think it is the right place.
Yoni Augarten

Yoni Augarten

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?
9:07 PM
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)
e

esspee

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
Yoni Augarten

Yoni Augarten

10/04/2022, 9:54 PM
Are you using a custom values file? If so, can you please share it?
e

esspee

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?
Yoni Augarten

Yoni Augarten

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)
6:12 AM
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 string
    authEncryptSecretKey: [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]
7:19 AM
@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?
e

esspee

10/05/2022, 7:20 AM
Yep that’s right. Only for learning to start with
Yoni Augarten

Yoni Augarten

10/05/2022, 7:20 AM
If that is the case, you should explicitly force the chart to spin up the database by adding the property:
localPostgres: true
You should also remove the
databaseConnectionString
property.
e

esspee

10/05/2022, 7:21 AM
Add the property in values.yaml?
Yoni Augarten

Yoni Augarten

10/05/2022, 7:21 AM
Yes.
e

esspee

10/05/2022, 7:22 AM
Sorry also to remove the whole secrets element in values?
Yoni Augarten

Yoni Augarten

10/05/2022, 7:23 AM
Only remove the databaseConnectionString property.
e

esspee

10/05/2022, 7:50 AM
I need to further it’s broken further after doing that
Yoni Augarten

Yoni Augarten

10/05/2022, 7:54 AM
Are you running into further problems?
e

esspee

10/05/2022, 7:56 AM
Yep pod resources issues. Must specify limits cpu, memory etc
Yoni Augarten

Yoni Augarten

10/05/2022, 8:05 AM
In order for me to assist, can you share the error you're facing in textual format?