Skip to content

Commit 1cd3870

Browse files
committed
edit HA prereq
1 parent 8a5ab43 commit 1cd3870

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed
Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,12 @@
1-
* If you are installing in high availability (HA) mode, a load balancer is required:
1+
- If you are installing in high availability (HA) mode, a load balancer is required. You can use the kURL internal load balancer or bring an external load balancer. An external load balancer might be preferred when clients outside the cluster need access to the cluster's Kubernetes API.
22

3-
* If the kURL Installer spec includes the EKCO add-on, you do not need to provide your own external load balancer. If you are going to use the internal load balancer, you can optionally preconfigure it by passing `| sudo bash -s ha ekco-enable-internal-load-balancer` with the kURL install command. Otherwise, you are prompted after running the kURL install command to specify that you want to use the internal load balancer.
4-
5-
* To use an external load balancer, ensure that your load balancer is:
6-
- A TCP forwarding external load balancer.
7-
- Configured to distribute traffic to all healthy control plane nodes in its target list.
3+
To install in HA mode, complete the following prerequisites:
4+
- (Optional) If you are going to use the kURL internal load balancer, you can preconfigure it by passing `| sudo bash -s ha ekco-enable-internal-load-balancer`.
5+
- To use an external load balancer, ensure that the load balancer meets the following requirements:
6+
- Must be a TCP forwarding load balancer
7+
- Must be configured to distribute traffic to all healthy control plane nodes in its target list
8+
- The health check must be a TCP check on port 6443
89

9-
If you are going to use an external load balancer, you can optionally preconfigured it by passing the `load-balancer-address=HOST:PORT` flag with the kURL install command. Otherwise, you are prompted after running the kURL install command to provide the address for the load balancer.
10+
For more information about how to create a load balancer for kube-apirserver, see [Create load balancer for kube-apiserver](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/high-availability/#create-load-balancer-for-kube-apiserver) in the Kubernetes documentation.
11+
12+
You can optionally preconfigure the external loader by passing the `load-balancer-address=HOST:PORT` flag with the kURL install command. Otherwise, you are prompted to provide the load balancer address after running the install command.

0 commit comments

Comments
 (0)