so deployed new version to my dev cluster (so copying keys here is ok, they get rotated): [12:55 PM] log from replicaset: lakefs Using config file: /etc/lakefs/config.yaml lakefs *time="2020-12-02T174924Z" level=info msg="lakeFS run" func="logging.(logrusEntryWrapper).Infof" file="build/logging/logger.go:111" version=0.18.0 lakefs time="2020-12-02T174924Z" level=info msg="connecting to the DB" func=db.ConnectDBPool file="build/db/connect.go:54" conn_max_lifetime=5m0s driver=pgx max_idle_conns=25 max_open_conns=25 uri="postgres://postgres:XXXXXXXXXX@postgresql.postgresql.svc:5432/postgres?sslmode=disable" lakefs time="2020-12-02T174924Z" level=info msg="initialized DB connection" func=db.ConnectDBPool file="build/db/connect.go:73" conn_max_lifetime=5m0s driver=pgx max_idle_conns=25 max_open_conns=25 uri="postgres://postgres:XXXXXXXXXX@postgresql.postgresql.svc:5432/postgres?sslmode=disable" lakefs time="2020-12-02T174924Z" level=fatal msg="Migration version mismatch, for more information see https://docs.lakefs.io/deploying/upgrade.html" func=cmd/lakefs/cmd.glob..func9 file="cmd/run.go:59" error="db schema version not compatible with latest version: db version=11, available=14"

As you say, you do need to migrate up. Could you do that as a step between stopping the old service and starting the new?

well, fluxcd automation does that for us

Okay... Clearly I'm going to have to read up on fluxcd.

take your time, np