Merge pull request #48244 from asa3311/sync-zh-153

[zh] sync self-subject-review-v1 replica-set-v1 cluster-upgrade

Author: k8s-ci-robot

content/zh-cn/docs/reference/kubernetes-api/authentication-resources/self-subject-review-v1.md

@@ -87,8 +87,12 @@ SelfSubjectReviewStatus 由 kube-apiserver 进行填充并发送回用户。
   - **userInfo.groups** ([]string)
 
     <!--
+    *Atomic: will be replaced during a merge*
+    
     The names of groups this user is a part of.
     -->
+    
+    **原子性：合并期间将被替换**
 
     此用户所属的用户组的名称。
 

content/zh-cn/docs/reference/kubernetes-api/workload-resources/replica-set-v1.md

@@ -164,6 +164,8 @@ ReplicaSetStatus 表示 ReplicaSet 的当前状态。
 - **conditions** ([]ReplicaSetCondition)
 
   *Patch strategy: merge on key `type`*
+
+  *Map: unique values on key type will be kept during a merge*
   
   Represents the latest available observations of a replica set's current state.
 
@@ -173,6 +175,8 @@ ReplicaSetStatus 表示 ReplicaSet 的当前状态。
 - **conditions** ([]ReplicaSetCondition)
 
   **补丁策略：按照键 `type` 合并**
+
+  **Map：键类型的唯一值将在合并期间保留**
 
   表示副本集当前状态的最新可用观测值。
 

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

@@ -14,13 +14,20 @@ weight: 350
 This page provides an overview of the steps you should follow to upgrade a
 Kubernetes cluster.
 
+The Kubernetes project recommends upgrading to the latest patch releases promptly, and
+to ensure that you are running a supported minor release of Kubernetes.
+Following this recommendation helps you to to stay secure.
+
 The way that you upgrade a cluster depends on how you initially deployed it
 and on any subsequent changes.
 
 At a high level, the steps you perform are:
 -->
 本页概述升级 Kubernetes 集群的步骤。
 
+Kubernetes 项目建议及时升级到最新的补丁版本，并确保使用受支持的 Kubernetes 版本。
+遵循这一建议有助于保障安全。
+
 升级集群的方式取决于你最初部署它的方式、以及后续更改它的方式。
 
 从高层规划的角度看，要执行的步骤是：