Merge pull request #32788 from my-git9/replicaset2

[zh] Update replicaset.md

content/zh/docs/concepts/workloads/controllers/replicaset.md

@@ -346,8 +346,6 @@ pod2             1/1     Running   0          36s
 
 As with all other Kubernetes API objects, a ReplicaSet needs the `apiVersion`, `kind`, and `metadata` fields.
 For ReplicaSets, the `kind` is always a ReplicaSet.
-In Kubernetes 1.9 the API version `apps/v1` on the ReplicaSet kind is the current version and is enabled by default. The API version `apps/v1beta2` is deprecated.
-Refer to the first lines of the `frontend.yaml` example for guidance.
 
 The name of a ReplicaSet object must be a valid
 [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
@@ -358,9 +356,6 @@ A ReplicaSet also needs a [`.spec` section](https://git.k8s.io/community/contrib
 
 与所有其他 Kubernetes API 对象一样，ReplicaSet 也需要 `apiVersion`、`kind`、和 `metadata` 字段。
 对于 ReplicaSets 而言，其 `kind` 始终是 ReplicaSet。
-在 Kubernetes 1.9 中，ReplicaSet 上的 API 版本 `apps/v1` 是其当前版本，且被
-默认启用。API 版本 `apps/v1beta2` 已被废弃。
-参考 `frontend.yaml` 示例的第一行。
 
 ReplicaSet 对象的名称必须是合法的
 [DNS 子域名](/zh/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)。