Merge pull request #3954 from jtravee/cluster-init-verbiage

Added note to clarify K3s versioning caveat for migration to etcd
This commit is contained in:
Jen Travinski
2022-03-15 11:28:51 -04:00
committed by GitHub
@@ -32,3 +32,5 @@ There are a few config flags that must be the same in all server nodes:
## Existing clusters
If you have an existing cluster using the default embedded SQLite database, you can convert it to etcd by simply restarting your K3s server with the `--cluster-init` flag. Once you've done that, you'll be able to add additional instances as described above.
>**Important:** K3s v1.22.2 and newer support migration from SQLite to etcd. Older versions will create a new empty datastore if you add `--cluster-init` to an existing server.