[zh-cn] sync configure-access-multiple-clusters debug-running-pod install-kubeadm (#41014)

Signed-off-by: xin.li <[email protected]>

Author: my-git9

content/zh-cn/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md

@@ -377,7 +377,7 @@ Install CNI plugins (required for most pod network):
 安装 CNI 插件（大多数 Pod 网络都需要）：
 
 ```bash
-CNI_PLUGINS_VERSION="v1.1.1"
+CNI_PLUGINS_VERSION="v1.2.0"
 ARCH="amd64"
 DEST="/opt/cni/bin"
 sudo mkdir -p "$DEST"
@@ -409,7 +409,7 @@ Install crictl (required for kubeadm / Kubelet Container Runtime Interface (CRI)
 安装 crictl（kubeadm/kubelet 容器运行时接口（CRI）所需）
 
 ```bash
-CRICTL_VERSION="v1.25.0"
+CRICTL_VERSION="v1.26.0"
 ARCH="amd64"
 curl -L "https://github.com/kubernetes-sigs/cri-tools/releases/download/${CRICTL_VERSION}/crictl-${CRICTL_VERSION}-linux-${ARCH}.tar.gz" | sudo tar -C $DOWNLOAD_DIR -xz
 ```

content/zh-cn/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md

@@ -575,13 +575,13 @@ It can be even more challenging if you are managing more than one cluster at the
 如果你同时管理多个集群，这可能会更具挑战性。
 
 <!--
-There is a `kubectl` alpha subcommand command to check subject attributes, such as username,
-for your selected Kubernetes client context: `kubectl alpha auth whoami`.
+There is a `kubectl` subcommand to check subject attributes, such as username, for your selected Kubernetes 
+client context: `kubectl auth whoami`.
 
 Read [API access to authentication information for a client](/docs/reference/access-authn-authz/authentication/#self-subject-review)
 to learn about this in more detail.
 -->
-对于你所选择的 Kubernetes 客户端上下文，有一个 `kubectl` Alpha 子命令可以检查用户名等主体属性：
+对于你所选择的 Kubernetes 客户端上下文，有一个 `kubectl` 子命令可以检查用户名等主体属性：
 `kubectl alpha auth whoami`。
 
 更多细节请参阅[通过 API 访问客户端的身份验证信息](/zh-cn/docs/reference/access-authn-authz/authentication/#self-subject-review)。

content/zh-cn/docs/tasks/debug/debug-application/debug-running-pod.md

@@ -891,7 +891,7 @@ When creating a debugging session on a node, keep in mind that:
 * The root filesystem of the Node will be mounted at `/host`.
 * The container runs in the host IPC, Network, and PID namespaces, although
   the pod isn't privileged, so reading some process information may fail,
-  and `chroot /host` will fail.
+  and `chroot /host` may fail.
 * If you need a privileged pod, create it manually.
 
 Don't forget to clean up the debugging Pod when you're finished with it:
@@ -900,7 +900,7 @@ Don't forget to clean up the debugging Pod when you're finished with it:
 * `kubectl debug` 基于节点的名字自动生成新的 Pod 的名字。
 * 节点的根文件系统会被挂载在 `/host`。
 * 新的调试容器运行在主机 IPC 名字空间、主机网络名字空间以及主机 PID 名字空间内，
-  Pod 没有特权，因此读取某些进程信息可能会失败，并且 `chroot /host` 也会失败。
+  Pod 没有特权，因此读取某些进程信息可能会失败，并且 `chroot /host` 也可能会失败。
 * 如果你需要一个特权 Pod，需要手动创建。
 
 当你完成节点调试时，不要忘记清理调试 Pod：