Skip to content

Commit 7f3bd92

Browse files
committed
[zh-cn] sync kubeadm/change-package-repository.md
Signed-off-by: xin.li <[email protected]>
1 parent 4cbc4ab commit 7f3bd92

File tree

1 file changed

+35
-5
lines changed

1 file changed

+35
-5
lines changed

content/zh-cn/docs/tasks/administer-cluster/kubeadm/change-package-repository.md

Lines changed: 35 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,16 +12,46 @@ weight: 120
1212
<!-- overview -->
1313

1414
<!--
15-
This page explains how to enable a package repository for a new Kubernetes minor release
15+
This page explains how to enable a package repository for the desired
16+
Kubernetes minor release upon upgrading a cluster. This is only needed
1617
for users of the community-owned package repositories hosted at `pkgs.k8s.io`.
17-
Unlike the legacy package repositories, the community-owned package repositories are
18-
structured in a way that there's a dedicated package repository for each Kubernetes
19-
minor version.
18+
Unlike the legacy package repositories, the community-owned package
19+
repositories are structured in a way that there's a dedicated package
20+
repository for each Kubernetes minor version.
2021
-->
21-
本文阐述如何为 `pkgs.k8s.io` 上托管的、社区自治的软件包仓库的用户,
22+
本页介绍了如何在升级集群时启用包含 Kubernetes 次要版本的软件包仓库。
23+
这仅适用于使用托管在 `pkgs.k8s.io` 上社区自治软件包仓库的用户。
2224
启用新的 Kubernetes 小版本的软件包仓库。与传统的软件包仓库不同,
2325
社区自治的软件包仓库所采用的结构为每个 Kubernetes 小版本都有一个专门的软件包仓库。
2426

27+
{{< note >}}
28+
<!--
29+
This guide only covers a part of the Kubernetes upgrade process. Please see the
30+
[upgrade guide](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) for
31+
more information about upgrading Kubernetes clusters.
32+
-->
33+
本指南仅介绍 Kubernetes 升级过程的一部分。
34+
有关升级 Kubernetes 集群的更多信息,
35+
请参阅[升级指南](/zh-cn/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)
36+
{{</ note >}}
37+
38+
{{< note >}}
39+
<!--
40+
This step is only needed upon upgrading a cluster to another **minor** release.
41+
If you're upgrading to another patch release within the same minor release (e.g.
42+
v{{< skew currentVersion >}}.5 to v{{< skew currentVersion >}}.7), you don't
43+
need to follow this guide. However, if you're still using the legacy package
44+
repositories, you'll need to migrate to the new community-owned package
45+
repositories before upgrading (see the next section for more details on how to
46+
do this).
47+
-->
48+
仅在将集群升级到另一个**次要**版本时才需要执行此步骤。
49+
如果你要升级到同一次要版本中的另一个补丁版本(例如:v{{< skew currentVersion >}}.5 到
50+
v{{< skew currentVersion >}}.7)则不需要遵循本指南。
51+
但是,如果你仍在使用旧的软件包仓库,则需要在升级之前迁移到社区自治的新软件包仓库
52+
(有关如何执行此操作的更多详细信息,请参阅下一节)。
53+
{{</ note >}}
54+
2555
## {{% heading "prerequisites" %}}
2656

2757
<!--

0 commit comments

Comments
 (0)