Hello, can you confirm that the helm chart does no...
# help
a
Hello, can you confirm that the helm chart does not support deploying lakefs using dynamodb as database? The database type seems to be hardcoded: https://github.com/treeverse/charts/blob/master/charts/lakefs/templates/_env.tpl#L3-L4
b
Hi @Alessandro Mangone yes, currently it is hard code - I'll open an issue to fix this one until tomorrow
👍🏻 1
👍 1
Pull-request merged with fix for the above.
a
Thank you @Barak Amar! But by having a look at the code I can’t find any reference to dynamodb? I’m looking at these lines, but I don’t know if they get overridden somewhere else.
(I’m not really proficient in helm charts syntax, so I might be missing something)
b
So, the change enables you to control the database type and additional configuration as part of
lakefsConfig
section in your variables.
Example:
create myvalues.yaml:
Copy code
secrets:
  authEncryptSecretKey: random_string
lakefsConfig: |
  database:
    type: local
  blockstore:
    type: local
and use it to install lakefs:
Copy code
$ helm install -f myvalues.yaml my-lakefs lakefs/lakefs
it will deploy lakefs with the above configuration - using local database and local block storage
in your case you can use 'database.type' 'dynamodb' (like in the example: https://docs.lakefs.io/reference/configuration.html#example-aws-deployment-with-dynamodb-database) to configure which table to use.
The change you referenced was made to keep the same defaults we had so far and enable any customization using lakefsConfig settings.
👍 1
a
Thanks for the clarification! I’ll try updating the chart right now
lakefs 1
Seems to be working as expected! Thanks for the quick update! 🙂
b
@Alessandro Mangone note I've update the above snippet with additional secret field as it is required.
👍 1
a
Yes I already had that from when I tried it using postgres, thanks