Skip to content

Commit cc5eb85

Browse files
authored
Merge pull request #34689 from tengqm/fix-install-kubeadm
[zh-cn] Fix install kubeadm page
2 parents 3945e74 + 6891091 commit cc5eb85

File tree

1 file changed

+18
-24
lines changed

1 file changed

+18
-24
lines changed

content/zh-cn/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md

Lines changed: 18 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -172,40 +172,33 @@ for more information.
172172
参阅[容器运行时](/zh-cn/docs/setup/production-environment/container-runtimes/)
173173
以了解更多信息。
174174

175-
<!--
176175
{{< note >}}
176+
<!--
177177
Docker Engine does not implement the [CRI](/docs/concepts/architecture/cri/)
178178
which is a requirement for a container runtime to work with Kubernetes.
179179
For that reason, an additional service [cri-dockerd](https://github.com/Mirantis/cri-dockerd)
180180
has to be installed. cri-dockerd is a project based on the legacy built-in
181181
Docker Engine support that was [removed](/dockershim) from the kubelet in version 1.24.
182182
-->
183-
184-
{{< note >}}
185183
Docker Engine 没有实现 [CRI](/zh-cn/docs/concepts/architecture/cri/),而这是容器运行时在 Kubernetes 中工作所需要的。
186184
为此,必须安装一个额外的服务 [cri-dockerd](https://github.com/Mirantis/cri-dockerd)
187185
cri-dockerd 是一个基于传统的内置Docker引擎支持的项目,它在 1.24 版本从 kubelet 中[移除](/zh-cn/dockershim)
188186
{{< /note >}}
189187

190188
<!--
191189
The tables below include the known endpoints for supported operating systems:
192-
193-
{{< tabs name="container_runtime" >}}
194-
{{% tab name="Linux" %}}
195190
-->
196191
下面的表格包括被支持的操作系统的已知端点。
197192

198193
{{< tabs name="container_runtime" >}}
199194
{{% tab name="Linux" %}}
200195

201196
<!--
202-
{{< table >}}
203197
| Runtime | Path to Unix domain socket |
204198
|------------------------------------|----------------------------------------------|
205199
| containerd | `unix:///var/run/containerd/containerd.sock` |
206200
| CRI-O | `unix:///var/run/crio/crio.sock` |
207201
| Docker Engine (using cri-dockerd) | `unix:///var/run/cri-dockerd.sock` |
208-
{{< /table >}}
209202
-->
210203
{{< table >}}
211204
| 运行时 | Unix 域套接字 |
@@ -215,17 +208,14 @@ The tables below include the known endpoints for supported operating systems:
215208
| Docker Engine (使用 cri-dockerd) | `unix:///var/run/cri-dockerd.sock` |
216209
{{< /table >}}
217210

218-
<!--
211+
{{% /tab %}}
219212
{{% tab name="Windows" %}}
220-
221-
{{< table >}}
213+
<!--
222214
| Runtime | Path to Windows named pipe |
223215
|------------------------------------|----------------------------------------------|
224216
| containerd | `npipe:////./pipe/containerd-containerd` |
225217
| Docker Engine (using cri-dockerd) | `npipe:////./pipe/cri-dockerd` |
226-
{{< /table >}}
227218
-->
228-
{{% tab name="Windows" %}}
229219

230220
{{< table >}}
231221
| 运行时 | Windows 命名管道路径 |
@@ -234,6 +224,9 @@ The tables below include the known endpoints for supported operating systems:
234224
| Docker Engine (使用 cri-dockerd) | `npipe:////./pipe/cri-dockerd` |
235225
{{< /table >}}
236226

227+
{{% /tab %}}
228+
{{< /tabs >}}
229+
237230
<!--
238231
## Installing kubeadm, kubelet and kubectl
239232
@@ -245,16 +238,6 @@ You will install these packages on all of your machines:
245238
and does things like starting pods and containers.
246239
247240
* `kubectl`: the command line util to talk to your cluster.
248-
249-
kubeadm **will not** install or manage `kubelet` or `kubectl` for you, so you will
250-
need to ensure they match the version of the Kubernetes control plane you want
251-
kubeadm to install for you. If you do not, there is a risk of a version skew occurring that
252-
can lead to unexpected, buggy behaviour. However, _one_ minor version skew between the
253-
kubelet and the control plane is supported, but the kubelet version may never exceed the API
254-
server version. For example, kubelets running 1.7.0 should be fully compatible with a 1.8.0 API server,
255-
but not vice versa.
256-
257-
For information about installing `kubectl`, see [Install and set up kubectl](/docs/tasks/tools/).
258241
-->
259242
## 安装 kubeadm、kubelet 和 kubectl
260243

@@ -266,6 +249,17 @@ For information about installing `kubectl`, see [Install and set up kubectl](/do
266249

267250
* `kubectl`:用来与集群通信的命令行工具。
268251

252+
<!--
253+
kubeadm **will not** install or manage `kubelet` or `kubectl` for you, so you will
254+
need to ensure they match the version of the Kubernetes control plane you want
255+
kubeadm to install for you. If you do not, there is a risk of a version skew occurring that
256+
can lead to unexpected, buggy behaviour. However, _one_ minor version skew between the
257+
kubelet and the control plane is supported, but the kubelet version may never exceed the API
258+
server version. For example, kubelets running 1.7.0 should be fully compatible with a 1.8.0 API server,
259+
but not vice versa.
260+
261+
For information about installing `kubectl`, see [Install and set up kubectl](/docs/tasks/tools/).
262+
-->
269263
kubeadm **不能** 帮你安装或者管理 `kubelet``kubectl`,所以你需要
270264
确保它们与通过 kubeadm 安装的控制平面的版本相匹配。
271265
如果不这样做,则存在发生版本偏差的风险,可能会导致一些预料之外的错误和问题。
@@ -390,7 +384,6 @@ sudo systemctl enable --now kubelet
390384

391385
{{% /tab %}}
392386
{{% tab name="无包管理器的情况" %}}
393-
394387
<!--
395388
Install CNI plugins (required for most pod network):
396389
-->
@@ -522,3 +515,4 @@ If you are running into difficulties with kubeadm, please consult our [troublesh
522515
* [Using kubeadm to Create a Cluster](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)
523516
-->
524517
* [使用 kubeadm 创建集群](/zh-cn/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)
518+

0 commit comments

Comments
 (0)