Skip to content

Commit 936d798

Browse files
DynamicKubeletConfig has not been supported in kubeadm for a while.
1 parent 12c57e6 commit 936d798

File tree

1 file changed

+0
-46
lines changed

1 file changed

+0
-46
lines changed

content/en/docs/reference/setup-tools/kubeadm/implementation-details.md

Lines changed: 0 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -298,26 +298,6 @@ Please note that:
298298
2. in case of kubeadm is executed in the `--dry-run` mode, the etcd static Pod manifest is written in a temporary folder
299299
3. Static Pod manifest generation for local etcd can be invoked individually with the [`kubeadm init phase etcd local`](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/#cmd-phase-etcd) command
300300

301-
### Optional Dynamic Kubelet Configuration
302-
303-
To use this functionality call `kubeadm alpha kubelet config enable-dynamic`. It writes the kubelet init configuration
304-
into `/var/lib/kubelet/config/init/kubelet` file.
305-
306-
The init configuration is used for starting the kubelet on this specific node, providing an alternative for the kubelet drop-in file;
307-
such configuration will be replaced by the kubelet base configuration as described in following steps.
308-
See [set kubelet parameters via a config file](/docs/tasks/administer-cluster/kubelet-config-file) for additional information.
309-
310-
Please note that:
311-
312-
1. To make dynamic kubelet configuration work, flag `--dynamic-config-dir=/var/lib/kubelet/config/dynamic` should be specified
313-
in `/etc/systemd/system/kubelet.service.d/10-kubeadm.conf`
314-
1. The kubelet configuration can be changed by passing a `KubeletConfiguration` object to `kubeadm init` or `kubeadm join` by using
315-
a configuration file `--config some-file.yaml`. The `KubeletConfiguration` object can be separated from other objects such
316-
as `InitConfiguration` using the `---` separator. For more details have a look at the `kubeadm config print-default` command.
317-
318-
For more details about the `KubeletConfiguration` struct, take a look at the
319-
[`KubeletConfiguration` reference](/docs/reference/config-api/kubelet-config.v1beta1/).
320-
321301
### Wait for the control plane to come up
322302

323303
kubeadm waits (upto 4m0s) until `localhost:6443/healthz` (kube-apiserver liveness) returns `ok`. However in order to detect
@@ -327,17 +307,6 @@ deadlock conditions, kubeadm fails fast if `localhost:10255/healthz` (kubelet li
327307
kubeadm relies on the kubelet to pull the control plane images and run them properly as static Pods.
328308
After the control plane is up, kubeadm completes the tasks described in following paragraphs.
329309

330-
### (optional) Write base kubelet configuration
331-
332-
{{< feature-state for_k8s_version="v1.11" state="beta" >}}
333-
334-
If kubeadm is invoked with `--feature-gates=DynamicKubeletConfig`:
335-
336-
1. Write the kubelet base configuration into the `kubelet-base-config-v1.9` ConfigMap in the `kube-system` namespace
337-
2. Creates RBAC rules for granting read access to that ConfigMap to all bootstrap tokens and all kubelet instances
338-
(that is `system:bootstrappers:kubeadm:default-node-token` and `system:nodes` groups)
339-
3. Enable the dynamic kubelet configuration feature for the initial control-plane node by pointing `Node.spec.configSource` to the newly-created ConfigMap
340-
341310
### Save the kubeadm ClusterConfiguration in a ConfigMap for later reference
342311

343312
kubeadm saves the configuration passed to `kubeadm init` in a ConfigMap named `kubeadm-config` under `kube-system` namespace.
@@ -520,18 +489,3 @@ Please note that:
520489
- The temporary authentication resolve to a user member of `system:bootstrappers:kubeadm:default-node-token` group which was granted
521490
access to CSR api during the `kubeadm init` process
522491
- The automatic CSR approval is managed by the csrapprover controller, according with configuration done the `kubeadm init` process
523-
524-
### (optional) Write init kubelet configuration
525-
526-
{{< feature-state for_k8s_version="v1.11" state="beta" >}}
527-
528-
If kubeadm is invoked with `--feature-gates=DynamicKubeletConfig`:
529-
530-
1. Read the kubelet base configuration from the `kubelet-base-config-v1.x` ConfigMap in the `kube-system` namespace using the
531-
Bootstrap Token credentials, and write it to disk as kubelet init configuration file `/var/lib/kubelet/config/init/kubelet`
532-
2. As soon as kubelet starts with the Node's own credential (`/etc/kubernetes/kubelet.conf`), update current node configuration
533-
specifying that the source for the node/kubelet configuration is the above ConfigMap.
534-
535-
Please note that:
536-
537-
1. To make dynamic kubelet configuration work, flag `--dynamic-config-dir=/var/lib/kubelet/config/dynamic` should be specified in `/etc/systemd/system/kubelet.service.d/10-kubeadm.conf`

0 commit comments

Comments
 (0)