Skip to content

Commit 94d9812

Browse files
committed
sync reconfigure-kubelet.md to the latest with en version
1 parent 6a5ee2f commit 94d9812

File tree

1 file changed

+13
-20
lines changed

1 file changed

+13
-20
lines changed

content/zh/docs/tasks/administer-cluster/reconfigure-kubelet.md

Lines changed: 13 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,13 @@ content_type: task
1717

1818
<!--
1919
{{< caution >}}
20-
[Dynamic Kubelet Configuration](https://github.com/kubernetes/enhancements/issues/281)
20+
The [Dynamic Kubelet Configuration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/281-dynamic-kubelet-configuration)
2121
feature is deprecated and should not be used.
2222
Please switch to alternative means distributing configuration to the Nodes of your cluster.
2323
{{< /caution >}}
2424
-->
2525
{{< caution >}}
26-
[动态 kubelet 配置](https://github.com/kubernetes/enhancements/issues/281)
26+
[动态 kubelet 配置](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/281-dynamic-kubelet-configuration)
2727
已经废弃不建议使用。请选择其他方法将配置分发到集群中的节点。
2828
{{< /caution >}}
2929

@@ -57,22 +57,15 @@ fields is available in the inline
5757

5858
<!--
5959
You need to have a Kubernetes cluster.
60-
You also need kubectl v1.11 or higher, configured to communicate with your cluster.
60+
You also need `kubectl`, [installed](/docs/tasks/tools/#kubectl) and configured to communicate with your cluster.
61+
Make sure that you are using a version of `kubectl` that is
62+
[compatible](/releases/version-skew-policy/) with your cluster.
6163
{{< version-check >}}
62-
Your cluster API server version (eg v1.12) must be no more than one minor
63-
version away from the version of kubectl that you are using. For example,
64-
if your cluster is running v1.16 then you can use kubectl v1.15, v1.16
65-
or v1.17; other combinations
66-
[aren't supported](/docs/setup/release/version-skew-policy/#kubectl).
6764
-->
6865
你需要一个 Kubernetes 集群。
69-
你需要 v1.11 或更高版本的 kubectl并配置好与集群的通信。
66+
你还需要 `kubectl`[安装](/zh/docs/tasks/tools/#kubectl)并配置好与集群的通信。
7067
{{< version-check >}}
71-
你的集群 API 服务器版本(如 v1.12)不能和你的 kubectl
72-
版本相差超过一个小版本号。
73-
例如,如果你的集群在运行 v1.16,那么你可以使用 v1.15、v1.16、v1.17 的 kubectl,
74-
所有其他的组合都是
75-
[不支持的](/zh/docs/setup/release/version-skew-policy/#kubectl)
68+
确保你使用的 `kubectl` 版本与集群 [兼容](/releases/version-skew-policy/)
7669

7770
<!--
7871
Some of the examples use the command line tool
@@ -658,15 +651,15 @@ internal failure, see Kubelet log for details | 在对配置进行同步的循
658651
## {{% heading "whatsnext" %}}
659652

660653
<!--
661-
- For more information on configuring the kubelet via a configuration file, see
662-
[Set kubelet parameters via a config file](/docs/tasks/administer-cluster/kubelet-config-file).
663-
- See the reference documentation for [`NodeConfigSource`](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#nodeconfigsource-v1-core)
654+
- [Set kubelet parameters via a config file](/docs/tasks/administer-cluster/kubelet-config-file)
655+
explains the supported way to configure a kubelet.
656+
- See the reference documentation for Node, including the `configSource` field within
657+
the Node's [.spec](/docs/reference/kubernetes-api/cluster-resources/node-v1/#NodeSpec)
664658
- Learn more about kubelet configuration by checking the
665659
[`KubeletConfiguration`](/docs/reference/config-api/kubelet-config.v1beta1/)
666660
reference.
667661
-->
668-
- 关于如何通过配置文件来配置 kubelet 的更多细节信息,可参阅
669-
[使用配置文件设置 kubelet 参数](/zh/docs/tasks/administer-cluster/kubelet-config-file).
670-
- 阅读 API 文档中 [`NodeConfigSource`](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#nodeconfigsource-v1-core) 说明
662+
- [使用配置文件设置 kubelet 参数](/zh/docs/tasks/administer-cluster/kubelet-config-file)说明了配置 kubelet 的方法。
663+
- 阅读 Node 的参考文档,包括 [.spec](/docs/reference/kubernetes-api/cluster-resources/node-v1/#NodeSpec) 里的 `configSource` 字段
671664
- 查阅[`KubeletConfiguration`](/docs/reference/config-api/kubelet-config.v1beta1/)文献进一步了解 kubelet
672665
配置信息。

0 commit comments

Comments
 (0)