From fd558f0d948ea24165332bb740f0e487a5b6a096 Mon Sep 17 00:00:00 2001
From: Liz <33235082+liztio@users.noreply.github.com>
Date: Mon, 25 Jun 2018 17:51:22 -0400
Subject: [PATCH] Documentation on setting node name with Kubeadm (#8925)

* Documentation on setting node name with Kubeadm

* copyedit
---
 .../en/docs/reference/setup-tools/kubeadm/kubeadm-init.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md
index a9fdedd005..d163b1a2eb 100644
--- a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md
+++ b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md
@@ -429,6 +429,14 @@ In order to set up a cluster where the master and worker nodes communicate with
 
 3. Finally, when you run `kubeadm join`, make sure you provide the private IP of the API server addressed as defined in step 1.
 
+### Setting the node name
+
+By default, `kubeadm` assigns a node name based on a machine's host address. You can override this setting with the  `--node-name`flag.
+The flag passes the appropriate [`--hostname-override`](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) 
+to the kubelet.
+
+Be aware that overriding the hostname can [interfere with cloud providers](https://github.com/kubernetes/website/pull/8873).
+
 ### Self-hosting the Kubernetes control plane {#self-hosting}
 
 As of 1.8, you can experimentally create a _self-hosted_ Kubernetes control