From a3db9fb85da049473ae2c2f23e918c89ea9725d8 Mon Sep 17 00:00:00 2001 From: Li Zebang Date: Wed, 22 Aug 2018 02:49:27 +0800 Subject: [PATCH] something wrong in kubelet-integration.md (#9974) * Propogating not "Propogating", is "Propagating" * `kubelet init` and `kubelet join` `kubeadm init` and `kubeadm join`, not `kubelet init` and `kubelet join` --- content/en/docs/setup/independent/kubelet-integration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/setup/independent/kubelet-integration.md b/content/en/docs/setup/independent/kubelet-integration.md index 80836bdd0e..574fe4d421 100644 --- a/content/en/docs/setup/independent/kubelet-integration.md +++ b/content/en/docs/setup/independent/kubelet-integration.md @@ -35,9 +35,9 @@ kubelet configurations centrally](#configure-kubelets-using-kubeadm). The following sections describe patterns to kubelet configuration that are simplified by using kubeadm, rather than managing the kubelet configuration for each Node manually. -### Propogating cluster-level configuration to each kubelet +### Propagating cluster-level configuration to each kubelet -You can provide the kubelet with default values to be used by `kubelet init` and `kubelet join` +You can provide the kubelet with default values to be used by `kubeadm init` and `kubeadm join` commands. Interesting examples include using a different CRI runtime or setting the default subnet used by services.