From f218c25778a6dffff0bd81e00feb50429d60b062 Mon Sep 17 00:00:00 2001 From: Mitesh Jain <47820816+miteshskj@users.noreply.github.com> Date: Tue, 5 Apr 2022 21:56:52 +0530 Subject: [PATCH 1/2] Remove stale information about apiVersion. --- content/en/docs/concepts/workloads/controllers/replicaset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/replicaset.md b/content/en/docs/concepts/workloads/controllers/replicaset.md index 1daf567c66..0917eb1002 100644 --- a/content/en/docs/concepts/workloads/controllers/replicaset.md +++ b/content/en/docs/concepts/workloads/controllers/replicaset.md @@ -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. 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. The name of a ReplicaSet object must be a valid From 1a5fe3ccbb6f27a9f5144dd2f0214df2365b7474 Mon Sep 17 00:00:00 2001 From: Mitesh Jain <47820816+miteshskj@users.noreply.github.com> Date: Wed, 6 Apr 2022 00:49:09 +0530 Subject: [PATCH 2/2] Remove stale information about apiVersion. --- content/en/docs/concepts/workloads/controllers/replicaset.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/replicaset.md b/content/en/docs/concepts/workloads/controllers/replicaset.md index 0917eb1002..8024e6246a 100644 --- a/content/en/docs/concepts/workloads/controllers/replicaset.md +++ b/content/en/docs/concepts/workloads/controllers/replicaset.md @@ -223,8 +223,6 @@ 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. For ReplicaSets, the `kind` is always a ReplicaSet. -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. The name of a ReplicaSet object must be a valid [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).