From 8a2f0d35b147a65b8928aa5fc30ffce5abf74a4f Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Mon, 14 Oct 2019 08:51:45 +0100 Subject: [PATCH] Reword glossary entry for ReplicaSet Explain what a ReplicaSet is, rather than what a ReplicationController isn't. --- content/en/docs/reference/glossary/replica-set.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/en/docs/reference/glossary/replica-set.md b/content/en/docs/reference/glossary/replica-set.md index e2c09eed59b16..a5676015ca0ff 100755 --- a/content/en/docs/reference/glossary/replica-set.md +++ b/content/en/docs/reference/glossary/replica-set.md @@ -4,7 +4,7 @@ id: replica-set date: 2018-04-12 full_link: /docs/concepts/workloads/controllers/replicaset/ short_description: > - ReplicaSet is the next-generation Replication Controller. + ReplicaSet ensures that a specified number of Pod replicas are running at one time aka: tags: @@ -12,8 +12,10 @@ tags: - core-object - workload --- - ReplicaSet is the next-generation Replication Controller. + A ReplicaSet (aims to) maintain a set of replica Pods running at any given time. - + -ReplicaSet, like ReplicationController, ensures that a specified number of pods replicas are running at one time. ReplicaSet supports the new set-based selector requirements as described in the labels user guide, whereas a Replication Controller only supports equality-based selector requirements. +Workload objects such as {{< glossary_tooltip term_id="deployment" >}} make use of ReplicaSets +to ensure that the configured number of {{< glossary_tooltip term_id="pod" text="Pods" >}} are +running in your cluster, based on the spec of that ReplicaSet.