Add documentation for automatic etcd migration

Should help with https://github.com/k3s-io/k3s/issues/1257
This commit is contained in:
Andrew Garrett
2022-02-04 00:26:45 +11:00
committed by GitHub
parent dbac3af771
commit 92371ed7dd
@@ -29,3 +29,6 @@ There are a few config flags that must be the same in all server nodes:
* Network related flags: `--cluster-dns`, `--cluster-domain`, `--cluster-cidr`, `--service-cidr`
* Flags controlling the deployment of certain components: `--disable-helm-controller`, `--disable-kube-proxy`, `--disable-network-policy` and any component passed to `--disable`
* Feature related flags: `--secrets-encryption`
## 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.