You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
How to migrate standalone k3s to existing External datastore backed K3s Cluster (multi-node) #4648
Is your feature request related to a problem? Please describe.
This is not a feature request but just a question. If we have a k3s single node cluster running on a local datastore (default), how can we migrate to existing k3s multi-node cluster running with external datastore (e.g. MariaDB) without affecting the running workloads.
Describe the solution you'd like
When a k3s standalone node joins the existing cluster, the existing workloads should not be affected.
Describe alternatives you've considered
No alternative.
We don't currently support migrating from one Kine sql backend to another, say from sqlite to mysql. We do support migrating from sqlite to etcd; all you need to do is start an existing standalone node with --cluster-init.
Activity
brandond commentedon Dec 7, 2021
We don't currently support migrating from one Kine sql backend to another, say from sqlite to mysql. We do support migrating from sqlite to etcd; all you need to do is start an existing standalone node with --cluster-init.