From 35e904d7c3d1f41405ff53f23127a4d54b8a843d Mon Sep 17 00:00:00 2001 From: opethema <110918373+opethema@users.noreply.github.com> Date: Sat, 29 Jun 2024 03:42:06 +0200 Subject: [PATCH] fix image and kube-vip links (#11267) --- docs/operations/ha-mode.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/operations/ha-mode.md b/docs/operations/ha-mode.md index f961c7462..64e8c025b 100644 --- a/docs/operations/ha-mode.md +++ b/docs/operations/ha-mode.md @@ -30,12 +30,12 @@ loadbalancer. If you wish to control the name of the loadbalancer container, you can set the variable `loadbalancer_apiserver_pod_name`. If you choose to NOT use the local internal loadbalancer, you will need to -use the [kube-vip](kube-vip.md) ansible role or configure your own loadbalancer to achieve HA. By default, it only configures a non-HA endpoint, which points to the +use the [kube-vip](/docs/ingress/kube-vip.md) ansible role or configure your own loadbalancer to achieve HA. By default, it only configures a non-HA endpoint, which points to the `access_ip` or IP address of the first server node in the `kube_control_plane` group. It can also configure clients to use endpoints for a given loadbalancer type. The following diagram shows how traffic to the apiserver is directed. - + A user may opt to use an external loadbalancer (LB) instead. An external LB provides access for external clients, while the internal LB accepts client -- GitLab