@@ -257,34 +257,42 @@ When you run `kubeadm join`, kubeadm uses the Bootstrap Token credential to perf
257
257
a TLS bootstrap, which fetches the credential needed to download the
258
258
` kubelet-config-1.X` ConfigMap and writes it to `/var/lib/kubelet/config.yaml`. The dynamic
259
259
environment file is generated in exactly the same way as `kubeadm init`.
260
+ -->
261
+
262
+ # ## 当使用 `kubeadm join`时的工作流程
260
263
264
+ 当运行 `kubeadm join` 时,kubeadm 使用 Bootstrap Token 证书执行 TLS 引导,该引导会获取一份证书,
265
+ 该证书需要下载 `kubelet-config-1.X` ConfigMap 并把它写入 `/var/lib/kubelet/config.yaml` 中。
266
+ 动态环境文件的生成方式恰好与 `kubeadm init` 完全相同。
267
+
268
+ <!--
261
269
Next, `kubeadm` runs the following two commands to load the new configuration into the kubelet :
270
+ -->
271
+ 接下来,`kubeadm` 运行以下两个命令将新配置加载到 kubelet 中:
262
272
263
273
` ` ` bash
264
274
systemctl daemon-reload && systemctl restart kubelet
265
275
` ` `
266
276
277
+ <!--
267
278
After the kubelet loads the new configuration, kubeadm writes the
268
279
` /etc/kubernetes/bootstrap-kubelet.conf` KubeConfig file, which contains a CA certificate and Bootstrap
269
280
Token. These are used by the kubelet to perform the TLS Bootstrap and obtain a unique
270
- credential, which is stored in `/etc/kubernetes/kubelet.conf`. When this file is written, the kubelet
271
- has finished performing the TLS Bootstrap.
281
+ credential, which is stored in `/etc/kubernetes/kubelet.conf`.
272
282
-->
273
- # ## 当使用 `kubeadm join`时的工作流程
274
-
275
- 当运行 `kubeadm join` 时,kubeadm 使用 Bootstrap Token 证书执行 TLS 引导,该引导会获取一份证书,该证书需要下载 `kubelet-config-1.X` ConfigMap 并把它写入 `/var/lib/kubelet/config.yaml` 中。
276
- 动态环境文件的生成方式恰好与 `kubeadm init` 相同。
277
-
278
- 接下来,kubeadm 运行以下两个命令将新配置加载到 kubelet 中:
279
-
280
- ` ` ` bash
281
- systemctl daemon-reload && systemctl restart kubelet
282
- ` ` `
283
283
284
284
在 kubelet 加载新配置后,kubeadm 将写入 `/etc/kubernetes/bootstrap-kubelet.conf` KubeConfig 文件中,
285
285
该文件包含 CA 证书和引导程序令牌。
286
286
kubelet 使用这些证书执行 TLS 引导程序并获取唯一的凭据,该凭据被存储在 `/etc/kubernetes/kubelet.conf` 中。
287
- 当此文件被写入后,kubelet 就完成了执行 TLS 引导程序。
287
+
288
+ <!--
289
+ When the `/etc/kubernetes/kubelet.conf` file is written, the kubelet has finished performing the TLS Bootstrap.
290
+ Kubeadm deletes the `/etc/kubernetes/bootstrap-kubelet.conf` file after completing the TLS Bootstrap.
291
+ -->
292
+
293
+ 当 `/etc/kubernetes/kubelet.conf` 文件被写入后,kubelet 就完成了 TLS 引导过程。
294
+ Kubeadm 在完成 TLS 引导过程后将删除 `/etc/kubernetes/bootstrap-kubelet.conf` 文件。
295
+
288
296
289
297
<!--
290
298
# # The kubelet drop-in file for systemd
0 commit comments