kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove stale information about apiVersion.

This commit is contained in:
Mitesh Jain 2022-04-05 21:56:52 +05:30
parent 3cadb66eb8
commit f218c25778
No known key found for this signature in database
GPG Key ID: E397C9E72FBFEE6F
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/concepts/workloads/controllers/replicaset.md
View File

@ -223,7 +223,7 @@ In this manner, a ReplicaSet can own a non-homogenous set of Pods
As with all other Kubernetes API objects, a ReplicaSet needs the `apiVersion`, `kind`, and `metadata` fields. As with all other Kubernetes API objects, a ReplicaSet needs the `apiVersion`, `kind`, and `metadata` fields.
For ReplicaSets, the `kind` is always a ReplicaSet. 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. The API version `apps/v1` on the ReplicaSet kind is the current version and is enabled by default.
Refer to the first lines of the `frontend.yaml` example for guidance. Refer to the first lines of the `frontend.yaml` example for guidance.
The name of a ReplicaSet object must be a valid The name of a ReplicaSet object must be a valid