From 7b3c93a1b6d36aa6fc026f3a90f8fe69b218f51b Mon Sep 17 00:00:00 2001 From: Mikhail Kozorovitskiy Date: Wed, 22 Jul 2020 15:41:08 -0500 Subject: [PATCH] Deconflict DQLite future Removing sentence that indicates DQLite will be the option used in the future. Linked to https://github.com/rancher/k3s/issues/2050 --- content/k3s/latest/en/installation/ha-embedded/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/k3s/latest/en/installation/ha-embedded/_index.md b/content/k3s/latest/en/installation/ha-embedded/_index.md index 58526b65280..23911da6399 100644 --- a/content/k3s/latest/en/installation/ha-embedded/_index.md +++ b/content/k3s/latest/en/installation/ha-embedded/_index.md @@ -3,7 +3,7 @@ title: "High Availability with Embedded DB (Experimental)" weight: 40 --- -As of v1.0.0, K3s is previewing support for running a highly available control plane without the need for an external database. This means there is no need to manage an external etcd or SQL datastore in order to run a reliable production-grade setup. While this feature is currently experimental, we expect it to be the primary architecture for running HA K3s clusters in the future. +As of v1.0.0, K3s is previewing support for running a highly available control plane without the need for an external database. This means there is no need to manage an external etcd or SQL datastore in order to run a reliable production-grade setup. This architecture is achieved by embedding a dqlite database within the K3s server process. DQLite is short for "distributed SQLite." According to https://dqlite.io, it is "*a fast, embedded, persistent SQL database with Raft consensus that is perfect for fault-tolerant IoT and Edge devices.*" This makes it a natural fit for K3s.