From a51b259cc8cb3363636eb035d748ea585084cf88 Mon Sep 17 00:00:00 2001 From: David Nuzik Date: Mon, 11 Nov 2019 17:12:51 -0700 Subject: [PATCH] HA fixes for comments in GH issue - Addresses 2 comments about the HA page: https://github.com/rancher/k3s/issues/1031#issuecomment-552672334 https://github.com/rancher/k3s/issues/1031#issuecomment-552673219 --- content/k3s/latest/en/installation/ha/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/k3s/latest/en/installation/ha/_index.md b/content/k3s/latest/en/installation/ha/_index.md index bf7edf5bed3..bd6436ef948 100644 --- a/content/k3s/latest/en/installation/ha/_index.md +++ b/content/k3s/latest/en/installation/ha/_index.md @@ -13,9 +13,9 @@ For production environments that cannot tolerate down time, we recommend install 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` +* A load balancer to expose the Kubernetes API for clients such as kubectl and to expose a stable k3s worker registration endpoint -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. +The external database shown should be a single endpoint k3s can access. 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 --------------------