From d5060a9173ab4811cba8b31fbe5f431a66eea08e Mon Sep 17 00:00:00 2001 From: "Lubomir I. Ivanov" Date: Wed, 9 Oct 2019 02:33:52 +0300 Subject: [PATCH] kubeadm: update notes for joining with discovery file (#16557) --- .../en/docs/reference/setup-tools/kubeadm/kubeadm-join.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-join.md b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-join.md index 2cff0b810d..3183af005c 100644 --- a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-join.md +++ b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-join.md @@ -171,9 +171,9 @@ In case the discovery file does not contain credentials, the TLS discovery token **Disadvantages:** - Requires that you have some way to carry the discovery information from - the control-plane node to the bootstrapping nodes. This might be possible, for example, - via your cloud provider or provisioning tool. The information in this file is - not secret, but HTTPS or equivalent is required to ensure its integrity. + the control-plane node to the bootstrapping nodes. If the discovery file contains credentials + you must keep it secret and transfer it over a secure channel. This might be possible with your + cloud provider or provisioning tool. ### Securing your installation even more {#securing-more}