Skip to content

Commit 0050ad9

Browse files
author
Mengjiao Liu
committed
[zh]Add 2022-01-07-kubernetes-is-moving-on-from-dockershim.md
1 parent 6708ea3 commit 0050ad9

File tree

1 file changed

+199
-0
lines changed

1 file changed

+199
-0
lines changed

‎content/zh/blog/_posts/2022-01-07-kubernetes-is-moving-on-from-dockershim.md

Lines changed: 199 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,199 @@
1+
---
2+
layout: blog
3+
title: "Kubernetes 即将移除 Dockershim：承诺和下一步"
4+
date: 2022-01-07
5+
slug: kubernetes-is-moving-on-from-dockershim
6+
---
7+
<!--
8+
layout: blog
9+
title: "Kubernetes is Moving on From Dockershim: Commitments and Next Steps"
10+
date: 2022-01-07
11+
slug: kubernetes-is-moving-on-from-dockershim
12+
-->
13+
14+
<!--
15+
**Authors:** Sergey Kanzhelev (Google), Jim Angel (Google), Davanum Srinivas (VMware), Shannon Kularathna (Google), Chris Short (AWS), Dawn Chen (Google)
16+
-->
17+
**作者：** Sergey Kanzhelev (Google), Jim Angel (Google), Davanum Srinivas (VMware), Shannon Kularathna (Google), Chris Short (AWS), Dawn Chen (Google)
18+
19+
<!--
20+
Kubernetes is removing dockershim in the upcoming v1.24 release. We're excited
21+
to reaffirm our community values by supporting open source container runtimes,
22+
enabling a smaller kubelet, and increasing engineering velocity for teams using
23+
Kubernetes. If you [use Docker Engine as a container runtime](/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use/)
24+
for your Kubernetes cluster, get ready to migrate in 1.24! To check if you're
25+
affected, refer to [Check whether dockershim deprecation affects you](/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/).
26+
-->
27+
Kubernetes 将在即将发布的 1.24 版本中移除 dockershim。我们很高兴能够通过支持开源容器运行时、支持更小的
28+
kubelet 以及为使用 Kubernetes 的团队提高工程速度来重申我们的社区价值。
29+
如果你[使用 Docker Engine 作为 Kubernetes 集群的容器运行时](/zh/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use/)，
30+
请准备好在 1.24 中迁移！要检查你是否受到影响，
31+
请参考[检查弃用 Dockershim 对你的影响](/zh/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/)。
32+
33+
<!--
34+
## Why we’re moving away from dockershim
35+
36+
Docker was the first container runtime used by Kubernetes. This is one of the
37+
reasons why Docker is so familiar to many Kubernetes users and enthusiasts.
38+
Docker support was hardcoded into Kubernetes – a component the project refers to
39+
as dockershim.
40+
-->
41+
## 为什么我们要离开 dockershim {#why-we-re-moving-away-from-dockershim}
42+
43+
Docker 是 Kubernetes 使用的第一个容器运行时。
44+
这也是许多 Kubernetes 用户和爱好者如此熟悉 Docker 的原因之一。
45+
对 Docker 的支持被硬编码到 Kubernetes 中——一个被项目称为 dockershim 的组件。
46+
<!--
47+
As containerization became an industry standard, the Kubernetes project added support
48+
for additional runtimes. This culminated in the implementation of the
49+
container runtime interface (CRI), letting system components (like the kubelet)
50+
talk to container runtimes in a standardized way. As a result, dockershim became
51+
an anomaly in the Kubernetes project.
52+
-->
53+
随着容器化成为行业标准，Kubernetes 项目增加了对其他运行时的支持。
54+
最终实现了容器运行时接口（CRI），让系统组件（如 kubelet）以标准化的方式与容器运行时通信。
55+
因此，dockershim 成为了 Kubernetes 项目中的一个异常现象。
56+
<!--
57+
Dependencies on Docker and dockershim have crept into various tools
58+
and projects in the CNCF ecosystem ecosystem, resulting in fragile code.
59+
60+
By removing the
61+
dockershim CRI, we're embracing the first value of CNCF: "[Fast is better than
62+
slow](https://github.com/cncf/foundation/blob/master/charter.md#3-values)".
63+
Stay tuned for future communications on the topic!
64+
-->
65+
对 Docker 和 dockershim 的依赖已经渗透到 CNCF 生态系统中的各种工具和项目中，这导致了代码脆弱。
66+
67+
通过删除 dockershim CRI，我们拥抱了 CNCF 的第一个价值：
68+
“[快比慢好](https://github.com/cncf/foundation/blob/master/charter.md#3-values)”。
69+
请继续关注未来关于这个话题的交流!
70+
71+
<!--
72+
## Deprecation timeline
73+
74+
We [formally announced](/blog/2020/12/08/kubernetes-1-20-release-announcement/) the dockershim deprecation in December 2020. Full removal is targeted
75+
in Kubernetes 1.24, in April 2022. This timeline
76+
aligns with our [deprecation policy](/docs/reference/using-api/deprecation-policy/#deprecating-a-feature-or-behavior),
77+
which states that deprecated behaviors must function for at least 1 year
78+
after their announced deprecation.
79+
-->
80+
## 弃用时间线 {#deprecation-timeline}
81+
82+
我们[正式宣布](/zh/blog/2020/12/08/kubernetes-1-20-release-announcement/)于
83+
2020 年 12 月弃用 dockershim。目标是在 2022 年 4 月，
84+
Kubernetes 1.24 中完全移除 dockershim。
85+
此时间线与我们的[弃用策略](/zh/docs/reference/using api/deprecation-policy/#deprecating-a-feature-or-behavior)一致，
86+
即规定已弃用的行为必须在其宣布弃用后至少运行 1 年。
87+
88+
<!--
89+
We'll support Kubernetes version 1.23, which includes
90+
dockershim, for another year in the Kubernetes project. For managed
91+
Kubernetes providers, vendor support is likely to last even longer, but this is
92+
dependent on the companies themselves. Regardless, we're confident all cluster operations will have
93+
time to migrate. If you have more questions about the dockershim removal, refer
94+
to the [Dockershim Deprecation FAQ](/dockershim).
95+
-->
96+
包括 dockershim 的 Kubernetes 1.23 版本，在 Kubernetes 项目中将再支持一年。
97+
对于托管 Kubernetes 的供应商，供应商支持可能会持续更长时间，但这取决于公司本身。
98+
无论如何，我们相信所有集群操作都有时间进行迁移。如果你有更多关于 dockershim 移除的问题，
99+
请参考[弃用 Dockershim 的常见问题](/zh/blog/2020/12/02/dockershim-faq/)。
100+
101+
<!--
102+
We asked you whether you feel prepared for the migration from dockershim in this
103+
survey: [Are you ready for Dockershim removal](/blog/2021/11/12/are-you-ready-for-dockershim-removal/).
104+
We had over 600 responses. To everybody who took time filling out the survey,
105+
thank you.
106+
-->
107+
在这个[你是否为 dockershim 的删除做好了准备](/blog/2021/11/12/are-you-ready-for-dockershim-removal/)的调查中，
108+
我们询问你是否为 dockershim 的迁移做好了准备。我们收到了 600 多个回复。
109+
感谢所有花时间填写调查问卷的人。
110+
111+
<!--
112+
The results show that we still have a lot of ground to cover to help you to
113+
migrate smoothly. Other container runtimes exist, and have been promoted
114+
extensively. However, many users told us they still rely on dockershim,
115+
and sometimes have dependencies that need to be re-worked. Some of these
116+
dependencies are outside of your control. Based on your feedback, here are some
117+
of the steps we are taking to help.
118+
-->
119+
结果表明，在帮助你顺利迁移方面，我们还有很多工作要做。
120+
存在其他容器运行时，并且已被广泛推广。但是，许多用户告诉我们他们仍然依赖 dockershim，
121+
并且有时需要重新处理依赖项。其中一些依赖项超出控制范围。
122+
根据收集到的反馈，我们采取了一些措施提供帮助。
123+
124+
<!--
125+
## Our next steps
126+
127+
Based on the feedback you provided:
128+
129+
- CNCF and the 1.24 release team are committed to delivering documentation in
130+
time for the 1.24 release. This includes more informative blog posts like this
131+
one, updating existing code samples, tutorials, and tasks, and producing a
132+
migration guide for cluster operators.
133+
- We are reaching out to the rest of the CNCF community to help prepare them for
134+
this change.
135+
-->
136+
## 我们的下一个步骤 {#our-next-steps}
137+
138+
根据提供的反馈：
139+
140+
- CNCF 和 1.24 版本团队致力于及时交付 1.24 版本的文档。这包括像本文这样的包含更多信息的博客文章，
141+
更新现有的代码示例、教程和任务，并为集群操作人员生成迁移指南。
142+
- 我们正在联系 CNCF 社区的其他成员，帮助他们为这一变化做好准备。
143+
144+
<!--
145+
If you're part of a project with dependencies on dockershim, or if you're
146+
interested in helping with the migration effort, please join us! There's always
147+
room for more contributors, whether to our transition tools or to our
148+
documentation. To get started, say hello in the
149+
[#sig-node](https://kubernetes.slack.com/archives/C0BP8PW9G)
150+
channel on [Kubernetes Slack](https://slack.kubernetes.io/)!
151+
-->
152+
如果你是依赖 dockershim 的项目的一部分，或者如果你有兴趣帮助参与迁移工作，请加入我们！
153+
无论是我们的迁移工具还是我们的文档，总是有更多贡献者的空间。
154+
作为起步，请在 [Kubernetes Slack](https://slack.kubernetes.io/) 上的
155+
[#sig-node](https://kubernetes.slack.com/archives/C0BP8PW9G) 频道打个招呼！
156+
157+
<!--
158+
## Final thoughts
159+
160+
As a project, we've already seen cluster operators increasingly adopt other
161+
container runtimes through 2021.
162+
We believe there are no major blockers to migration. The steps we're taking to
163+
improve the migration experience will light the path more clearly for you.
164+
-->
165+
## 最终想法 {#final-thoughts}
166+
167+
作为一个项目，我们已经看到集群运营商在 2021 年之前越来越多地采用其他容器运行时。
168+
我们相信迁移没有主要障碍。我们为改善迁移体验而采取的步骤将为你指明更清晰的道路。
169+
170+
<!--
171+
We understand that migration from dockershim is yet another action you may need to
172+
do to keep your Kubernetes infrastructure up to date. For most of you, this step
173+
will be straightforward and transparent. In some cases, you will encounter
174+
hiccups or issues. The community has discussed at length whether postponing the
175+
dockershim removal would be helpful. For example, we recently talked about it in
176+
the [SIG Node discussion on November 11th](https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit#bookmark=id.r77y11bgzid)
177+
and in the [Kubernetes Steering committee meeting held on December 6th](https://docs.google.com/document/d/1qazwMIHGeF3iUh5xMJIJ6PDr-S3bNkT8tNLRkSiOkOU/edit#bookmark=id.m0ir406av7jx).
178+
We already [postponed](https://github.com/kubernetes/enhancements/pull/2481/) it
179+
once in 2021 because the adoption rate of other
180+
runtimes was lower than we wanted, which also gave us more time to identify
181+
potential blocking issues.
182+
-->
183+
我们知道，从 dockershim 迁移是你可能需要执行的另一项操作，以保证你的 Kubernetes 基础架构保持最新。
184+
对于你们中的大多数人来说，这一步将是简单明了的。在某些情况下，你会遇到问题。
185+
社区已经详细讨论了推迟 dockershim 删除是否会有所帮助。
186+
例如，我们最近在 [11 月 11 日的 SIG Node 讨论](https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit#bookmark=id.r77y11bgzid)和
187+
[12 月 6 日 Kubernetes Steering 举行的委员会会议](https://docs.google.com/document/d/1qazwMIHGeF3iUh5xMJIJ6PDr-S3bNkT8tNLRkSiOkOU/edit#bookmark=id.m0ir406av7jx)谈到了它。
188+
我们已经在 2021 年[推迟](https://github.com/kubernetes/enhancements/pull/2481/)它一次，
189+
因为其他运行时的采用率低于我们的预期，这也给了我们更多的时间来识别潜在的阻塞问题。
190+
191+
<!--
192+
At this point, we believe that the value that you (and Kubernetes) gain from
193+
dockershim removal makes up for the migration effort you'll have. Start planning
194+
now to avoid surprises. We'll have more updates and guides before Kubernetes
195+
1.24 is released.
196+
-->
197+
在这一点上，我们相信你（和 Kubernetes）从移除 dockershim 中获得的价值可以弥补你将要进行的迁移工作。
198+
现在就开始计划以避免出现意外。在 Kubernetes 1.24 发布之前，我们将提供更多更新信息和指南。
199+

0 commit comments

Comments
 (0)