Thomas06/01/2023, 3:10 PM
. My pod is running but it isn't ready to use and I don't have more logs... I think the problem comes from my configuration in values.yaml file but I've tested several others without success. Have any of you had a similar failed deployment?
Failed to to get AWS account ID for BI
Thomas06/02/2023, 9:30 AM
variable in the blockstore part of the lakefsConfig but I got an incorrect key error. But I'm interested if you have the correct syntax for adding s3-related variables directly to the chart. And for the lakeFS pod, it tried to restart yes but I've this error:
Back-off restarting failed container
Thomas06/02/2023, 9:45 AM
Values file for helm that include the lakefs configuration and our secrets - `lfs-pgs-values.yaml`:
apiVersion: v1 kind: Secret metadata: name: barak-lakefs-env-secrets type: Opaque data: LAKEFS_BLOCKSTORE_S3_CREDENTIALS_ACCESS_KEY_ID: "<base64 s3 key>" LAKEFS_BLOCKSTORE_S3_CREDENTIALS_SECRET_ACCESS_KEY: "<base64 s3 secret>" LAKEFS_DATABASE_POSTGRES_CONNECTION_STRING: "<base64 database connection string>"
You can setup additional configuration for lakeFS in the above map - any secrets just assign it to the associated environment variable in the secrets file. The env var name are the for each lakefs configuration is LAKEFS_<uppercase + '_' instead of '.' to address the key>.
secrets: authEncryptSecretKey: "<encryption secret key>" extraEnvVarsSecret: barak-lakefs-env-secrets lakefsConfig: | database: type: postgres blockstore: type: s3 s3: region: us-east-1
The above assume you have a working postgres that lakeFS can connect to. Alt. you can use helm to install one too to try it out.
# first apply the secrets $ kubectl apply -f lfs-pgs-secrets.yaml # install our helm chart $ helm install -f lfs-pgs-values.yaml my-lakefs lakefs/lakefs