sync cluster-upgrade kubelet-credential-provider running-cloud-controller

Author: asa3311

content/zh-cn/docs/tasks/administer-cluster/cluster-upgrade.md

@@ -116,6 +116,15 @@ kubelet, or upgrade the kubelet on that node and bring the node back into servic
 然后使用一个运行了 kubelet {{< skew currentVersion >}} 版本的新节点替换它；
 或者升级此节点的 kubelet，并使节点恢复服务。
 
+{{< caution >}}
+<!--
+Draining nodes before upgrading kubelet ensures that pods are re-admitted and containers are
+re-created, which may be necessary to resolve some security issues or other important bugs.
+-->
+在升级 kubelet 之前先进行节点排空，这样可以确保 Pod 被重新准入并且容器被重新创建。
+这一步骤对于解决某些安全问题或其他关键错误是非常必要的。
+{{</ caution >}}
+
 <!--
 ### Other deployments {#upgrade-other}
 

content/zh-cn/docs/tasks/administer-cluster/kubelet-credential-provider.md

@@ -1,6 +1,5 @@
 ---
 title: 配置 kubelet 镜像凭据提供程序
-description: 配置 kubelet 的镜像凭据提供程序插件
 content_type: task
 min-kubernetes-server-version: v1.26
 weight: 120
@@ -11,7 +10,6 @@ title: Configure a kubelet image credential provider
 reviewers:
 - liggitt
 - cheftako
-description: Configure the kubelet's image credential provider plugin
 content_type: task
 min-kubernetes-server-version: v1.26
 weight: 120

content/zh-cn/docs/tasks/administer-cluster/running-cloud-controller.md

@@ -83,17 +83,14 @@ Successfully running cloud-controller-manager requires some changes to your clus
 你需要对集群配置做适当的修改以成功地运行云管理控制器：
 
 <!--
-* `kube-apiserver` and `kube-controller-manager` MUST NOT specify the `--cloud-provider`
- flag. This ensures that it does not run any cloud specific loops that would be run by
- cloud controller manager. In the future, this flag will be deprecated and removed.
-* `kubelet` must run with `--cloud-provider=external`. This is to ensure that the
- kubelet is aware that it must be initialized by the cloud controller manager
- before it is scheduled any work.
+* `kubelet`, `kube-apiserver`, and `kube-controller-manager` must be set according to the
+ user's usage of external CCM. If the user has an external CCM (not the internal cloud
+ controller loops in the Kubernetes Controller Manager), then `--cloud-provider=external`
+ must be specified. Otherwise, it should not be specified.
 -->
-* 一定不要为 `kube-apiserver` 和 `kube-controller-manager` 指定 `--cloud-provider` 标志。
- 这将保证它们不会运行任何云服务专用循环逻辑，这将会由云管理控制器运行。未来这个标记将被废弃并去除。
-* `kubelet` 必须使用 `--cloud-provider=external` 运行。
- 这是为了保证让 kubelet 知道在执行任何任务前，它必须被云管理控制器初始化。
+* `kubelet`、`kube-apiserver` 和 `kube-controller-manager` 必须根据用户对外部 CCM 的使用进行设置。
+ 如果用户有一个外部的 CCM（不是 Kubernetes 控制器管理器中的内部云控制器回路），
+ 那么必须添加 `--cloud-provider=external` 参数。否则，不应添加此参数。
 
 <!--
 Keep in mind that setting up your cluster to use cloud controller manager will
@@ -102,7 +99,7 @@ change your cluster behaviour in a few ways:
 请记住，设置集群使用云管理控制器将用多种方式更改集群行为：
 
 <!--
-* kubelets specifying `--cloud-provider=external` will add a taint
+* Components that specify `--cloud-provider=external` will add a taint
  `node.cloudprovider.kubernetes.io/uninitialized` with an effect `NoSchedule`
  during initialization. This marks the node as needing a second initialization
  from an external controller before it can be scheduled work. Note that in the
@@ -111,7 +108,7 @@ change your cluster behaviour in a few ways:
  require cloud specific information about nodes such as their region or type
  (high cpu, gpu, high memory, spot instance, etc).
 -->
-* 指定了 `--cloud-provider=external` 的 kubelet 将被添加一个 `node.cloudprovider.kubernetes.io/uninitialized`
+* 指定了 `--cloud-provider=external` 的组件将被添加一个 `node.cloudprovider.kubernetes.io/uninitialized`
  的污点，导致其在初始化过程中不可调度（`NoSchedule`）。
  这将标记该节点在能够正常调度前，需要外部的控制器进行二次初始化。
  请注意，如果云管理控制器不可用，集群中的新节点会一直处于不可调度的状态。