This message was deleted.

That's not a supported migration, so there's not a super easy way to do that.

OK, well, at least now I know. Makes me think twice about making the move. I might still do it because I have all the manifests / charts, but it's not just a migration.

@creamy-pencil-82913 any idea of the complexity of a scripted migration. I guess the db format must be straightforward KV, which might be generated from etcd dump ?

You could stand up a temporary standalone kine instance backed by your target DB, use an etcd client to dump the keys out of the current cluster and into kine, and then point k3s at the DB.

Nice. I guess it would me more complex if origin kine is not etcd (eg: moving from a mysql backend to a postgres backend) ?

Nah should work the same. You should be able to use an etcd client to do most things against kine.

tkhs @creamy-pencil-82913