https://lakefs.io/ logo
Join Slack
Powered by
Hey, in <LakeFS' installation instructions on Kube...
# help
c
Hey, in LakeFS' installation instructions on Kubernetes, the helm 
values.yaml
indicates I should include database connection strings and an encryption key:
Copy code
secrets:
    # replace this with the connection string of the database you created in a previous step:
    databaseConnectionString: [DATABASE_CONNECTION_STRING]
    # replace this with a randomly-generated string
    authEncryptSecretKey: [ENCRYPTION_SECRET_KEY]
-- but this is the first step, and the 
values.yaml
file is supplied to helm during installation. What is the expected process?
installing postgresql...
the default chart is missing database type: 
error="bad configuration: missing required keys: [database.type]" fields.file=/etc/lakefs/config.yaml
o
Hi @Chris Chart does contains: lakefsConfig: | database: type: local
c
This is what I see on the page:
Copy code
secrets:
    # replace this with the connection string of the database you created in a previous step:
    databaseConnectionString: [DATABASE_CONNECTION_STRING]
    # replace this with a randomly-generated string
    authEncryptSecretKey: [ENCRYPTION_SECRET_KEY]
lakefsConfig: |
    blockstore:
      type: s3
      s3:
        force_path_style: true
        endpoint: http://<minio_endpoint>
        discover_bucket_region: false
        credentials:
          access_key_id: <minio_access_key>
          secret_access_key: <minio_secret_key>
-- but I was able to get postgres working.
@Offir Cohen
Anyhow, now I am onto creating my first repo in Minio (locally deployed to kubernetes). I've configured it, but It looks like I am "failing to access storage". Looking for logs that have the access error...
Everything works! One last issue I hit was: • I have to create the bucket I reference when creating my first repo. Some indication that you cannot specify a bucket that does not exist, or some checkbox that indicated I wanted lakeFS to make the bucket would have been cool.
👍 1
This could be more painful than it seems. Ideally, I don't have to update MinIO and LakeFS independently when making a new repo. But at the moment, it looks like that is a requirement of any scripts/local or cloud deployment, etc.
I'll likely have to handle that in some other UI.
👍 1
ah, also 
lakectl config
awaits user input if I've already provided a configuration. I just happened to guess that is what it wanted (relevant doc page) -- if this isn't helping let me know. Just want LakeFS to be as frictionless as possible.
o
lakectl config awaits your input but defaults with the last known value. Create repository does require you to have the bucket created in your storage.
c
so the instructions as I run through the install process are: 1. put the access key/secret key and enpoint in 
~/.lakectl.yaml
according to the format ✅ 2. install lakectl/lakefs cli via brew ✅ 3. run 
lakectl config
(hangs until I press enter for each value it is reading/defaulting to from the config) a. many would have CTRL-C'd the hang rather than trying to press 'ENTER' and see what happened b. would they ever think to press 'ENTER'? I could see people getting stuck there.
o
Thanks for pointing this out. Please feel free to open a feature request
👍 1
c
ah, there is a bug. I'll make a bug report.
👍 1
ok, so new issue, and I may need help here. I have minio deployed to local kubernetes, which is accessible to the local environment via 
tcp
at the hostname 
localhost
after port forwarding. However, the DNS name for the minio service inside the kubernetes network is used instead when attempting to clone the data. What I need is for the local 
lakectl
tool to connect to the 
localhost
when it establishes a 
tcp
connection to minio rather than the kubernetes dns name. Right now, I have two paths: • update the hosts file and point, for example, 
minio.mlops.svc.cluster.local
to 
127.0.0.1
(which is the endpoint I configured in the lakefs helm 
values.yaml
) • configure the 
.lakectl.yaml
file to use 
127.0.0.1
for communication with minio The second will be easier to support for other users. Is there any way to configure 
lakectl.yaml
to use the localhost?
note the DNS trick worked -- just want to rule out ability to configure this, and I'll add this to my list of feature requests.
lakefs 1
3 Views
Open in Slack
PreviousNext
Powered by