From 5847d2cf24314e8561121c552eef61bfc0a6c2d4 Mon Sep 17 00:00:00 2001 From: RA489 Date: Thu, 11 Jul 2019 09:40:58 +0530 Subject: [PATCH] Issue with k8s.io/docs/setup/production-environment/tools/kubeadm/high-availability/ --- .../tools/kubeadm/high-availability.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md b/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md index dd29ca4b1ac04..3f7a4a4d74b0b 100644 --- a/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md +++ b/content/en/docs/setup/production-environment/tools/kubeadm/high-availability.md @@ -65,11 +65,8 @@ option. Your cluster requirements may need a different configuration. 1. Create a kube-apiserver load balancer with a name that resolves to DNS. - - In a cloud environment you should place your control plane nodes behind a TCP - forwarding load balancer. This load balancer distributes traffic to all - healthy control plane nodes in its target list. The health check for - an apiserver is a TCP check on the port the kube-apiserver listens on - (default value `:6443`). + - In a cloud environment, use the load balancer infrastructure provided by the cloud provider. + In an environment without a built-in load balancer (i.e. bare metal), you can use a TCP forwarding proxy,such as HAProxy, however you need to take steps to make that load balancer highly available. Otherwise your load balancer becomes a single point of failure. The health check for an apiserver is a TCP check on the port the kube-apiserver listens on (default value `:6443`). - It is not recommended to use an IP address directly in a cloud environment.