@@ -172,40 +172,33 @@ for more information.
172
172
参阅[ 容器运行时] ( /zh-cn/docs/setup/production-environment/container-runtimes/ )
173
173
以了解更多信息。
174
174
175
- <!--
176
175
{{< note >}}
176
+ <!--
177
177
Docker Engine does not implement the [CRI](/docs/concepts/architecture/cri/)
178
178
which is a requirement for a container runtime to work with Kubernetes.
179
179
For that reason, an additional service [cri-dockerd](https://github.com/Mirantis/cri-dockerd)
180
180
has to be installed. cri-dockerd is a project based on the legacy built-in
181
181
Docker Engine support that was [removed](/dockershim) from the kubelet in version 1.24.
182
182
-->
183
-
184
- {{< note >}}
185
183
Docker Engine 没有实现 [ CRI] ( /zh-cn/docs/concepts/architecture/cri/ ) ,而这是容器运行时在 Kubernetes 中工作所需要的。
186
184
为此,必须安装一个额外的服务 [ cri-dockerd] ( https://github.com/Mirantis/cri-dockerd ) 。
187
185
cri-dockerd 是一个基于传统的内置Docker引擎支持的项目,它在 1.24 版本从 kubelet 中[ 移除] ( /zh-cn/dockershim ) 。
188
186
{{< /note >}}
189
187
190
188
<!--
191
189
The tables below include the known endpoints for supported operating systems:
192
-
193
- {{< tabs name="container_runtime" >}}
194
- {{% tab name="Linux" %}}
195
190
-->
196
191
下面的表格包括被支持的操作系统的已知端点。
197
192
198
193
{{< tabs name="container_runtime" >}}
199
194
{{% tab name="Linux" %}}
200
195
201
196
<!--
202
- {{< table >}}
203
197
| Runtime | Path to Unix domain socket |
204
198
|------------------------------------|----------------------------------------------|
205
199
| containerd | `unix:///var/run/containerd/containerd.sock` |
206
200
| CRI-O | `unix:///var/run/crio/crio.sock` |
207
201
| Docker Engine (using cri-dockerd) | `unix:///var/run/cri-dockerd.sock` |
208
- {{< /table >}}
209
202
-->
210
203
{{< table >}}
211
204
| 运行时 | Unix 域套接字 |
@@ -215,17 +208,14 @@ The tables below include the known endpoints for supported operating systems:
215
208
| Docker Engine (使用 cri-dockerd) | ` unix:///var/run/cri-dockerd.sock ` |
216
209
{{< /table >}}
217
210
218
- <!--
211
+ {{% /tab %}}
219
212
{{% tab name="Windows" %}}
220
-
221
- {{< table >}}
213
+ <!--
222
214
| Runtime | Path to Windows named pipe |
223
215
|------------------------------------|----------------------------------------------|
224
216
| containerd | `npipe:////./pipe/containerd-containerd` |
225
217
| Docker Engine (using cri-dockerd) | `npipe:////./pipe/cri-dockerd` |
226
- {{< /table >}}
227
218
-->
228
- {{% tab name="Windows" %}}
229
219
230
220
{{< table >}}
231
221
| 运行时 | Windows 命名管道路径 |
@@ -234,6 +224,9 @@ The tables below include the known endpoints for supported operating systems:
234
224
| Docker Engine (使用 cri-dockerd) | ` npipe:////./pipe/cri-dockerd ` |
235
225
{{< /table >}}
236
226
227
+ {{% /tab %}}
228
+ {{< /tabs >}}
229
+
237
230
<!--
238
231
## Installing kubeadm, kubelet and kubectl
239
232
@@ -245,16 +238,6 @@ You will install these packages on all of your machines:
245
238
and does things like starting pods and containers.
246
239
247
240
* `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/).
258
241
-->
259
242
## 安装 kubeadm、kubelet 和 kubectl
260
243
@@ -266,6 +249,17 @@ For information about installing `kubectl`, see [Install and set up kubectl](/do
266
249
267
250
* ` kubectl ` :用来与集群通信的命令行工具。
268
251
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
+ -->
269
263
kubeadm ** 不能** 帮你安装或者管理 ` kubelet ` 或 ` kubectl ` ,所以你需要
270
264
确保它们与通过 kubeadm 安装的控制平面的版本相匹配。
271
265
如果不这样做,则存在发生版本偏差的风险,可能会导致一些预料之外的错误和问题。
@@ -390,7 +384,6 @@ sudo systemctl enable --now kubelet
390
384
391
385
{{% /tab %}}
392
386
{{% tab name="无包管理器的情况" %}}
393
-
394
387
<!--
395
388
Install CNI plugins (required for most pod network):
396
389
-->
@@ -522,3 +515,4 @@ If you are running into difficulties with kubeadm, please consult our [troublesh
522
515
* [Using kubeadm to Create a Cluster](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)
523
516
-->
524
517
* [ 使用 kubeadm 创建集群] ( /zh-cn/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/ )
518
+
0 commit comments