2018-05-05 16:00:51 +00:00
|
|
|
---
|
|
|
|
|
title: ReplicaSet
|
|
|
|
|
id: replica-set
|
|
|
|
|
date: 2018-04-12
|
2019-03-20 23:05:05 +00:00
|
|
|
full_link: /docs/concepts/workloads/controllers/replicaset/
|
2018-05-05 16:00:51 +00:00
|
|
|
short_description: >
|
2019-10-14 23:07:51 +00:00
|
|
|
ReplicaSet ensures that a specified number of Pod replicas are running at one time
|
2018-05-05 16:00:51 +00:00
|
|
|
|
|
|
|
|
aka:
|
|
|
|
|
tags:
|
|
|
|
|
- fundamental
|
|
|
|
|
- core-object
|
|
|
|
|
- workload
|
|
|
|
|
---
|
2019-10-14 23:07:51 +00:00
|
|
|
A ReplicaSet (aims to) maintain a set of replica Pods running at any given time.
|
2018-05-05 16:00:51 +00:00
|
|
|
|
2019-10-14 23:07:51 +00:00
|
|
|
<!--more-->
|
2018-05-05 16:00:51 +00:00
|
|
|
|
2019-10-14 23:07:51 +00:00
|
|
|
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.
|
