gang ye
10/30/2023, 6:04 AMstorage 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?Yoni Augarten
10/30/2023, 8:11 AMgang ye
10/30/2023, 4:47 PMimage:
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
postgres
. Updating itYoni Augarten
10/31/2023, 11:32 AM