From cff3e8fa959e3138cc94878c96ad3af66761e646 Mon Sep 17 00:00:00 2001 From: Jennifer Rondeau Date: Mon, 25 Jun 2018 14:59:40 -0400 Subject: [PATCH] copyedit --- content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 bebfaa534a563..06f7916a4b36a 100644 --- a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md +++ b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-init.md @@ -350,8 +350,8 @@ In order to set up a cluster where the master and worker nodes communicate with ### Setting the node name -By default, `kubeadm` will assign a node name based on a machine's host address. You can override this with `--node-name`. -Doing this will pass the appropriate [`--hostname-override`](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/#options) +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).