From fac8de54566b758bcf5655b9c248edd0de04d47d Mon Sep 17 00:00:00 2001 From: "xin.li" Date: Thu, 7 Apr 2022 09:28:44 +0800 Subject: [PATCH] [zh] Update replicaset.md Signed-off-by: xin.li --- content/zh/docs/concepts/workloads/controllers/replicaset.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/content/zh/docs/concepts/workloads/controllers/replicaset.md b/content/zh/docs/concepts/workloads/controllers/replicaset.md index 5e2e7954d4..ca92f8378e 100644 --- a/content/zh/docs/concepts/workloads/controllers/replicaset.md +++ b/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)。