whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reword glossary entry for ReplicaSet (#16886)

Browse Source 
Explain what a ReplicaSet is, rather than what a ReplicationController
isn't.
This commit is contained in:
Tim Bannister
2019-10-15 00:07:51 +01:00
committed by Kubernetes Prow Robot
parent 6a954bb700
commit 900ea77f57
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/glossary/replica-set.md
+5 -3
View File
@@ -4,7 +4,7 @@ id: replica-set
date: 2018-04-12 date: 2018-04-12
full_link: /docs/concepts/workloads/controllers/replicaset/ full_link: /docs/concepts/workloads/controllers/replicaset/
short_description: > short_description: >
ReplicaSet is the next-generation Replication Controller. ReplicaSet ensures that a specified number of Pod replicas are running at one time
aka: aka:
tags: tags:
@@ -12,8 +12,10 @@ tags:
- core-object - core-object
- workload - workload
--- ---
ReplicaSet is the next-generation Replication Controller. A ReplicaSet (aims to) maintain a set of replica Pods running at any given time.
<!--more--> <!--more-->
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.