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] 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).