diff --git a/content/k3s/latest/en/installation/ha/_index.md b/content/k3s/latest/en/installation/ha/_index.md index 0e700cdd6ac..73f4a3676cc 100644 --- a/content/k3s/latest/en/installation/ha/_index.md +++ b/content/k3s/latest/en/installation/ha/_index.md @@ -8,6 +8,15 @@ weight: 30 For production environments, we recommend installing k3s in a high-availability configuration so that you can always access your cluster. This procedure walks you through setting up a 2-node cluster with k3s with an external PostgreSQL database. As of v0.10.0 release (Experimental HA) we are supporting PostgreSQL 10.7-R1 thru 11.5-R1 +# Recommended Architecture +![k3s HA]({{< baseurl >}}/img/k3s/k3s-production-setup-v4.svg) +This image depicts a k3s HA install with two load balancers: + +* A load balancer to expose workloads to external traffic +* A load balancer to expose the Kubernetes API for worker node registration and admin access via `kubectl` + +The HA database shown should be a single endpoint k3s can access such as a load balancer. The worker registration / kubernetes API load balancer is needed if the master nodepool will be auto scaling and thus master nodes are ephemeral. Port 6443 is used for worker (agent) node registration and the Kubernetes API. + Installation Outline -------------------- 1. Create backend database (PostgreSQL) diff --git a/static/img/k3s/k3s-production-setup-v4.svg b/static/img/k3s/k3s-production-setup-v4.svg new file mode 100644 index 00000000000..c2fa54c57d7 --- /dev/null +++ b/static/img/k3s/k3s-production-setup-v4.svg @@ -0,0 +1 @@ +k3s-production-setup-v2 \ No newline at end of file