Hi team, I have one question about lakefs server s...
# help
g
Hi team, I have one question about lakefs server setup. I deployed it on K8s cluster with postgres and S3. Somehow the deployment gets restarted and then we need to config the repo again. If I use the same repo name and storage namespace, it will complain that
storage namespace already in use
. I thought that if we use same postgres and S3 path to persist data and metadata, the lakefs server should be able to restore from previous deployment status. It seems that is not the case. Is there any setting to avoid configure the lakefs server again during redeployment?
y
Hey @gang ye, if you're using the same database, everything should be persisted after a server restart. That includes your repositories and the commit history. It sounds like either the database is ephemeral, or that lakeFS is not really configured to work on top of the database. Could you share the lakeFS server configurations (or the Helm values file, if you're using the lakeFS Helm chart)?
g
Here is the helm chart configuration
Copy code
image:
  repository: <http://docker.apple.com/aiml-datainfra/lakefs|docker.apple.com/aiml-datainfra/lakefs>
  #repository: <http://docker.io/treeverse/lakefs|docker.io/treeverse/lakefs>
  tag: 1.0.0-amd64
  pullPolicy: IfNotPresent

# Keys used for existingSecret
secrets:
  authEncryptSecretKey: "123"
  databaseConnectionString: "<postgresql://user>:password***"

lakefsConfig: |
  logging.level: TRACE
  stats.enabled: false
  database:
    type: local
  blockstore:
    type: s3
    s3:
      region: us-west-2
      client_log_retries: true
      client_log_request: true

serviceAccount: 
  name: data-experimentation-sa

ingress:
  enabled: true
  annotations: 
    <http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: nginx
    <http://ingress.beta.kubernetes.io/sni|ingress.beta.kubernetes.io/sni>: "true"
    <http://nginx.ingress.kubernetes.io/force-ssl-redirect|nginx.ingress.kubernetes.io/force-ssl-redirect>: "true"
  hosts:
    - host: mlpt-test-data-experimentation.***
      paths:
        - /
  tls:
    - hosts: 
        - mlpt-test-data-experimentation.***
      secretName: mlpt-test-data-experimentation.***

service:
  port: 8000
I guess I know why. Database type misses to set to
postgres
. Updating it
y
@gang ye, seems like the problem indeed. Did it work?