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`pull/10024/head
parent
a5ec4953a5
commit
a3db9fb85d
|
@ -35,9 +35,9 @@ kubelet configurations centrally](#configure-kubelets-using-kubeadm).
|
||||||
The following sections describe patterns to kubelet configuration that are simplified by
|
The following sections describe patterns to kubelet configuration that are simplified by
|
||||||
using kubeadm, rather than managing the kubelet configuration for each Node manually.
|
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
|
commands. Interesting examples include using a different CRI runtime or setting the default subnet
|
||||||
used by services.
|
used by services.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue