What's Next?
Recap what was discussed in this chapter.
We'll cover the following
Summary#
The good news is that ReplicaSets are relatively straightforward. They provide a guarantee that the specified number of replicas of a Pod will be running in the system as long as there are available resources. That’s the primary and, arguably, the only purpose.
The bad news is that ReplicaSets are rarely used independently. You will almost never create a ReplicaSet directly just as you’re not going to create Pods. Instead, we tend to create ReplicaSets through Deployments. In other words, we use ReplicaSets to create and control Pods, and Deployments to create ReplicaSets (and a few other things). We’ll get to Deployment soon.
ℹ️ If you’d like to know more about ReplicaSets, please explore ReplicaSet v1 apps API documentation.
The above illustration shows and defines the Kubernetes components we have explored so far.
