Skip to content

Commit f481a2b

Browse files
authored
Merge pull request #32788 from my-git9/replicaset2
[zh] Update replicaset.md
2 parents f71cba2 + fac8de5 commit f481a2b

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

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

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -346,8 +346,6 @@ pod2 1/1 Running 0 36s
346346
347347
As with all other Kubernetes API objects, a ReplicaSet needs the `apiVersion`, `kind`, and `metadata` fields.
348348
For ReplicaSets, the `kind` is always a ReplicaSet.
349-
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.
350-
Refer to the first lines of the `frontend.yaml` example for guidance.
351349
352350
The name of a ReplicaSet object must be a valid
353351
[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
358356

359357
与所有其他 Kubernetes API 对象一样,ReplicaSet 也需要 `apiVersion``kind`、和 `metadata` 字段。
360358
对于 ReplicaSets 而言,其 `kind` 始终是 ReplicaSet。
361-
在 Kubernetes 1.9 中,ReplicaSet 上的 API 版本 `apps/v1` 是其当前版本,且被
362-
默认启用。API 版本 `apps/v1beta2` 已被废弃。
363-
参考 `frontend.yaml` 示例的第一行。
364359

365360
ReplicaSet 对象的名称必须是合法的
366361
[DNS 子域名](/zh/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)

0 commit comments

Comments
 (0)