From ff79a8a9ae057cffbadac738de1e7e80638ac689 Mon Sep 17 00:00:00 2001 From: facchettos Date: Tue, 13 Feb 2024 09:34:11 +0100 Subject: [PATCH] fixed link --- docs/pages/deploying-vclusters/high-availability.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/deploying-vclusters/high-availability.mdx b/docs/pages/deploying-vclusters/high-availability.mdx index 7d09ae2d7d..066525badd 100644 --- a/docs/pages/deploying-vclusters/high-availability.mdx +++ b/docs/pages/deploying-vclusters/high-availability.mdx @@ -153,7 +153,7 @@ In order to run vCluster with k3s as Kubernetes distribution in high availabilit * Create and use an [external datastore](./persistence.mdx) (as opposed to the embedded SQLite datastore used in single-server setups) * Run two or more k3s pods that will serve the Kubernetes API and run other control plane services -* You can also run k3s in high availability with the pro feature [embedded etcd](/pro/docs/features/high_availability) +* You can also run k3s in high availability with the pro feature [embedded etcd](../../pro/docs/features/high_availability) First create a `values.yaml` in the following form and make sure to change the connection string in `K3S_DATASTORE_ENDPOINT`: