Friday, March 18, 2022

ReplicaSet

A ReplicaSet is one of the K8 controllers that makes sure we have a specified number of pod replicas running.

 Its advance version of ReplicationController.

ReplicaSets allow us to use “set-based” label selector (e.g environment in (production, qa) or tier notin (frontend, backend)) as opposed to “equality-based”(e.g environment = production or tier != frontend) which is what you use with replication controller.

 

Replica Set ensures how many replica of pod should be running. It can be considered as a replacement of replication controller. The key difference between the replica set and the replication controller is, the replication controller only supports equality-based selector whereas the replica set supports set-based selector.


ReplicaSets are the successors to ReplicationControllers. The two serve the same purpose, and behave similarly, except that a ReplicationController does not support set-based selector requirements as described in the labels user guide. As such, ReplicaSets are preferred over ReplicationController

hhttps://kubernetes.io/docs/concepts/workloads/controllers/replicase



https://www.kubermatic.com/blog/introduction-to-kubernetes-replicasets/


https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/



t/

No comments:

Post a Comment

Sample Game App Deployment on EKS cluster

 https://padmakshi.medium.com/setting-up-an-eks-cluster-and-deploying-a-game-application-a-step-by-step-guide-08790e0be117