From 95ca85963ce4e5294db525d25445fb1877d49e1b Mon Sep 17 00:00:00 2001 From: steve-hardman <132999137+steve-hardman@users.noreply.github.com> Date: Fri, 9 Feb 2024 14:50:09 +0000 Subject: [PATCH] Mention 'exclude-from-external-load-balancers' in the kubeadm create cluster page (#45057) * Mention exclude-from-external-load-balancers * Mention exclude-from-external-load-balancers * Mention exclude-from-external-load-balancers Co-authored-by: Dipesh Rawat --------- Co-authored-by: Dipesh Rawat --- .../tools/kubeadm/create-cluster-kubeadm.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md index d441f09a6d2b3..dd30bc2fee3e0 100644 --- a/content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md +++ b/content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md @@ -383,6 +383,14 @@ This will remove the `node-role.kubernetes.io/control-plane:NoSchedule` taint from any nodes that have it, including the control plane nodes, meaning that the scheduler will then be able to schedule Pods everywhere. +Additionally, you can execute the following command to remove the +[`node.kubernetes.io/exclude-from-external-load-balancers`](/docs/reference/labels-annotations-taints/#node-kubernetes-io-exclude-from-external-load-balancers) label +from the control plane node, which excludes it from the list of backend servers: + +```bash +kubectl label nodes --all node.kubernetes.io/exclude-from-external-load-balancers- +``` + ### Joining your nodes {#join-nodes} The nodes are where your workloads (containers and Pods, etc) run. To add new nodes to your cluster do the following for each machine: