Merge pull request #51527 from asa3311/sync-zh-188

[zh] sync cri kubeadm-upgrade kustomization

Author: k8s-ci-robot

content/zh-cn/docs/concepts/architecture/cri.md

@@ -41,46 +41,42 @@ CRI 是一个插件接口，它使 kubelet 能够使用各种容器运行时，
 The kubelet acts as a client when connecting to the container runtime via gRPC.
 The runtime and image service endpoints have to be available in the container
 runtime, which can be configured separately within the kubelet by using the
-`--image-service-endpoint` [command line flags](/docs/reference/command-line-tools-reference/kubelet).
+`--container-runtime-endpoint`
+[command line flag](/docs/reference/command-line-tools-reference/kubelet/).
 -->
 当通过 gRPC 连接到容器运行时，kubelet 将充当客户端。运行时和镜像服务端点必须在容器运行时中可用，
-可以使用 `--image-service-endpoint`
+可以使用 `--container-runtime-endpoint`
 [命令行标志](/zh-cn/docs/reference/command-line-tools-reference/kubelet)在 kubelet 中单独配置。
 
 <!-- 
-For Kubernetes v{{< skew currentVersion >}}, the kubelet prefers to use CRI `v1`.
-If a container runtime does not support `v1` of the CRI, then the kubelet tries to
-negotiate any older supported version.
-The v{{< skew currentVersion >}} kubelet can also negotiate CRI `v1alpha2`, but
-this version is considered as deprecated.
-If the kubelet cannot negotiate a supported CRI version, the kubelet gives up
-and doesn't register as a node.
+For Kubernetes v1.26 and later, the kubelet requires that the container runtime
+supports the `v1` CRI API. If a container runtime does not support the `v1` API,
+the kubelet will not register the node.
 -->
-对 Kubernetes v{{< skew currentVersion >}}，kubelet 偏向于使用 CRI `v1` 版本。
-如果容器运行时不支持 CRI 的 `v1` 版本，那么 kubelet 会尝试协商较老的、仍被支持的所有版本。
-v{{< skew currentVersion >}} 版本的 kubelet 也可协商 CRI `v1alpha2` 版本，但该版本被视为已弃用。
-如果 kubelet 无法协商出可支持的 CRI 版本，则 kubelet 放弃并且不会注册为节点。
+对于 Kubernetes v1.26 及更高版本，
+kubelet 要求容器运行时必须支持 `v1` 版本的 CRI API。
+如果容器运行时不支持 `v1` API，kubelet 将不会注册该节点。
 
 <!-- 
 ## Upgrading
 
-When upgrading Kubernetes, the kubelet tries to automatically select the
-latest CRI version on restart of the component. If that fails, then the fallback
-will take place as mentioned above. If a gRPC re-dial was required because the
-container runtime has been upgraded, then the container runtime must also
-support the initially selected version or the redial is expected to fail. This
-requires a restart of the kubelet.
+When upgrading the Kubernetes version on a node, the kubelet restarts. If the
+container runtime does not support the `v1` CRI API, the kubelet will fail to
+register and report an error. If a gRPC re-dial is required because the container
+runtime has been upgraded, the runtime must support the `v1` CRI API for the
+connection to succeed. This might require a restart of the kubelet after the
+container runtime is correctly configured.
 -->
 ## 升级  {#upgrading}
 
-升级 Kubernetes 时，kubelet 会尝试在组件重启时自动选择最新的 CRI 版本。
-如果失败，则将如上所述进行回退。如果由于容器运行时已升级而需要 gRPC 重拨，
-则容器运行时还必须支持最初选择的版本，否则重拨预计会失败。
-这需要重新启动 kubelet。
+在节点上升级 Kubernetes 版本时，kubelet 会重新启动。
+如果容器运行时不支持 `v1` 版本的 CRI API，kubelet 将无法注册节点并报告错误。
+如果由于容器运行时已升级而需要重新建立 gRPC 连接，则该容器运行时必须支持 v1 版本的 CRI API，连接才能成功。
+在容器运行时正确配置后，可能需要重新启动 kubelet 才能建立连接。
 
 ## {{% heading "whatsnext" %}}
 
 <!-- 
 - Learn more about the CRI [protocol definition](https://github.com/kubernetes/cri-api/blob/c75ef5b/pkg/apis/runtime/v1/api.proto)
 -->
-- 了解更多有关 CRI [协议定义](https://github.com/kubernetes/cri-api/blob/c75ef5b/pkg/apis/runtime/v1/api.proto)
+- 了解更多有关 CRI [协议定义](https://github.com/kubernetes/cri-api/blob/v0.33.1/pkg/apis/runtime/v1/api.proto)

content/zh-cn/docs/tasks/manage-kubernetes-objects/kustomization.md

@@ -1116,7 +1116,7 @@ resources:
 images:
 - name: nginx
   newName: my.image.registry/nginx
-  newTag: 1.4.0
+  newTag: "1.4.0"
 EOF
 ```