[zh] Resync tasks pages (task-3)
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "从 dockershim 迁移"
|
||||
title: 从 dockershim 迁移
|
||||
weight: 10
|
||||
content_type: task
|
||||
no_list: true
|
||||
@@ -31,11 +31,11 @@ to understand the problem better.
|
||||
|
||||
<!--
|
||||
Dockershim was removed from Kubernetes with the release of v1.24.
|
||||
If you use Docker via dockershim as your container runtime, and wish to upgrade to v1.24,
|
||||
If you use Docker Engine via dockershim as your container runtime, and wish to upgrade to v1.24,
|
||||
it is recommended that you either migrate to another runtime or find an alternative means to obtain Docker Engine support.
|
||||
-->
|
||||
Dockershim 在 Kubernetes v1.24 版本已经被移除。
|
||||
如果你集群内是通过 dockershim 使用 Docker 作为容器运行时,并希望 Kubernetes 升级到 v1.24,
|
||||
如果你集群内是通过 dockershim 使用 Docker Engine 作为容器运行时,并希望 Kubernetes 升级到 v1.24,
|
||||
建议你迁移到其他容器运行时或使用其他方法以获得 Docker 引擎支持。
|
||||
|
||||
<!--
|
||||
@@ -58,19 +58,20 @@ configuration.
|
||||
These tasks will help you to migrate:
|
||||
|
||||
* [Check whether Dockershim deprecation affects you](/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/)
|
||||
* [Migrating from dockershim](/docs/tasks/administer-cluster/migrating-from-dockershim/)
|
||||
* [Migrate Docker Engine nodes from dockershim to cri-dockerd](/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd/)
|
||||
* [Migrating telemetry and security agents from dockershim](/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents/)
|
||||
-->
|
||||
你的集群中可以有不止一种类型的节点,尽管这不是常见的情况。
|
||||
|
||||
下面这些任务可以帮助你完成迁移:
|
||||
|
||||
* [检查弃用 Dockershim 对你的影响](/zh/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/)
|
||||
* [dockershim 迁移](/zh/docs/tasks/administer-cluster/migrating-from-dockershim/)
|
||||
* [检查弃用 Dockershim 是否影响到你](/zh/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/)
|
||||
* [将 Docker Engine 节点从 dockershim 迁移到 cri-dockerd](/zh/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd/)
|
||||
* [从 dockershim 迁移遥测和安全代理](/zh/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents/)
|
||||
<!--
|
||||
|
||||
## {{% heading "whatsnext" %}}
|
||||
|
||||
<!--
|
||||
* Check out [container runtimes](/docs/setup/production-environment/container-runtimes/)
|
||||
to understand your options for a container runtime.
|
||||
* There is a
|
||||
@@ -80,11 +81,9 @@ These tasks will help you to migrate:
|
||||
you can [report an issue](https://github.com/kubernetes/kubernetes/issues/new/choose)
|
||||
to the Kubernetes project.
|
||||
-->
|
||||
|
||||
## 下一步
|
||||
|
||||
* 查看[容器运行时](/zh/docs/setup/production-environment/container-runtimes/)了解可选的容器运行时。
|
||||
* [GitHub 问题](https://github.com/kubernetes/kubernetes/issues/106917)跟踪有关 dockershim 的弃用和删除的讨论。
|
||||
* [GitHub 问题](https://github.com/kubernetes/kubernetes/issues/106917)跟踪有关
|
||||
dockershim 的弃用和删除的讨论。
|
||||
* 如果你发现与 dockershim 迁移相关的缺陷或其他技术问题,
|
||||
可以在 Kubernetes 项目[报告问题](https://github.com/kubernetes/kubernetes/issues/new/choose)。
|
||||
|
||||
|
||||
|
||||
+11
-15
@@ -69,18 +69,15 @@ node-3 Ready v1.16.15 docker://19.3.1
|
||||
```
|
||||
<!--
|
||||
If your runtime shows as Docker Engine, you still might not be affected by the
|
||||
removal of dockershim in Kubernetes 1.24. [Check the runtime
|
||||
removal of dockershim in Kubernetes v1.24. [Check the runtime
|
||||
endpoint](#which-endpoint) to see if you use dockershim. If you don't use
|
||||
dockershim, you aren't affected.
|
||||
|
||||
For containerd, the output is similar to this:
|
||||
-->
|
||||
|
||||
如果你的容器运行时显示为 Docker Engine,你仍然可能不会被 1.24 中 dockershim 的移除所影响。
|
||||
如果你的容器运行时显示为 Docker Engine,你仍然可能不会被 v1.24 中 dockershim 的移除所影响。
|
||||
通过[检查运行时端点](#which-endpoint),可以查看你是否在使用 dockershim。
|
||||
如果你没有使用 dockershim,你就不会被影响。
|
||||
看下是否是使用的 dockershim,如何是 dockershim 则会受到在 Kubernetes 1.24 中移除 dockershim 的影响。
|
||||
反之则不会受到影响。
|
||||
|
||||
对于 containerd,输出类似于这样:
|
||||
|
||||
@@ -110,27 +107,24 @@ The container runtime talks to the kubelet over a Unix socket using the [CRI
|
||||
protocol](/docs/concepts/architecture/cri/), which is based on the gRPC
|
||||
framework. The kubelet acts as a client, and the runtime acts as the server.
|
||||
In some cases, you might find it useful to know which socket your nodes use. For
|
||||
example, with the removal of dockershim in Kubernetes 1.24 and later, you might
|
||||
example, with the removal of dockershim in Kubernetes v1.24 and later, you might
|
||||
want to know whether you use Docker Engine with dockershim.
|
||||
-->
|
||||
|
||||
容器运行时使用 Unix Socket 与 kubelet 通信,这一通信使用基于 gRPC 框架的
|
||||
[CRI 协议](/zh/docs/concepts/architecture/cri/)。kubelet 扮演客户端,运行时扮演服务器端。
|
||||
在某些情况下,你可能想知道你的节点使用的是哪个 socket。
|
||||
如若集群是 Kubernetes 1.24 及以后的版本,
|
||||
如若集群是 Kubernetes v1.24 及以后的版本,
|
||||
或许你想知道当前运行时是否是使用 dockershim 的 Docker Engine。
|
||||
|
||||
{{< note >}}
|
||||
<!--
|
||||
{{<note>}}
|
||||
If you currently use Docker Engine in your nodes with `cri-dockerd`, you aren't
|
||||
affected by the dockershim removal.
|
||||
{{</note>}}
|
||||
-->
|
||||
|
||||
{{<note>}}
|
||||
如果你的节点在通过 `cri-dockerd` 使用 Docker Engine,
|
||||
那么集群不会受到 Kubernetes 移除 dockershim 的影响。
|
||||
{{</note>}}
|
||||
{{< /note >}}
|
||||
|
||||
<!--
|
||||
You can check which socket you use by checking the kubelet configuration on your
|
||||
@@ -175,12 +169,14 @@ nodes.
|
||||
如若套接字 `unix:///run/containerd/containerd.sock` 是 containerd 的端点。
|
||||
|
||||
<!--
|
||||
If you use Docker Engine with the dockershim, [migrate to a different runtime](/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/),
|
||||
If you want to change the Container Runtime on a Node from Docker Engine to containerd,
|
||||
you can find out more information on [migrating from Docker Engine to containerd](/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/),
|
||||
or, if you want to continue using Docker Engine in v1.24 and later, migrate to a
|
||||
CRI-compatible adapter like [`cri-dockerd`](https://github.com/Mirantis/cri-dockerd).
|
||||
-->
|
||||
如果你通过 dockershim 来使用 Docker Engine,可在
|
||||
如果你将节点上的容器运行时从 Docker Engine 改变为 containerd,可在
|
||||
[迁移到不同的运行时](/zh/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/)
|
||||
找到更多信息。或者,如果你想在 Kubernetes v1.24 及以后的版本仍使用 Docker Engine,
|
||||
可以安装 CRI 兼容的适配器实现,如 [`cri-dockerd`](https://github.com/Mirantis/cri-dockerd)。
|
||||
[`cri-dockerd`](https://github.com/Mirantis/cri-dockerd)。
|
||||
[`cri-dockerd`](https://github.com/Mirantis/cri-dockerd)。
|
||||
|
||||
|
||||
Reference in New Issue
Block a user