Channels
announcements
blockers_for_windward
career-opportunities
celebrations
cuddle-corner
data-discussion
data-events
dev
events
general
help
iceberg-integration
lakefs-for-beginners
lakefs-hubspot-cloud-registration-email-automation
lakefs-releases
lakefs-suggestions
lakefs-twitter
linen-dev
memes-and-banter
say-hello
stackoverflow
test
Title
i
Iddo Avneri
10/04/2022, 6:53 PM@esspee, I’m reposting this here, since I think it is the right place.
y
Yoni Augarten
10/04/2022, 9:03 PMHey @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)
e
esspee
10/04/2022, 9:51 PMThanks. 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
y
Yoni Augarten
10/04/2022, 9:54 PMAre you using a custom values file? If so, can you please share it?
e
esspee
10/05/2022, 5:56 AMNo 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?
y
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)
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]@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 AMYep that’s right. Only for learning to start with
👍🏻 1
y
Yoni Augarten
10/05/2022, 7:20 AMIf that is the case, you should explicitly force the chart to spin up the database by adding the property:
localPostgres: truedatabaseConnectionStringe
esspee
10/05/2022, 7:21 AMAdd the property in values.yaml?
y
Yoni Augarten
10/05/2022, 7:21 AMYes.
e
esspee
10/05/2022, 7:22 AMSorry also to remove the whole secrets element in values?
y
Yoni Augarten
10/05/2022, 7:23 AMOnly remove the databaseConnectionString property.
e
esspee
10/05/2022, 7:50 AMI need to further it’s broken further after doing that
y
Yoni Augarten
10/05/2022, 7:54 AMAre you running into further problems?
e
esspee
10/05/2022, 7:56 AMYep pod resources issues. Must specify limits cpu, memory etc
y
Yoni Augarten
10/05/2022, 8:05 AMIn order for me to assist, can you share the error you're facing in textual format?