From 92371ed7dd323db57858038210c70fad5e3d1023 Mon Sep 17 00:00:00 2001 From: Andrew Garrett Date: Fri, 4 Feb 2022 00:26:45 +1100 Subject: [PATCH] Add documentation for automatic etcd migration Should help with https://github.com/k3s-io/k3s/issues/1257 --- content/k3s/latest/en/installation/ha-embedded/_index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/k3s/latest/en/installation/ha-embedded/_index.md b/content/k3s/latest/en/installation/ha-embedded/_index.md index 9526a67c61e..9d4a1d85cc6 100644 --- a/content/k3s/latest/en/installation/ha-embedded/_index.md +++ b/content/k3s/latest/en/installation/ha-embedded/_index.md @@ -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.