IBM :: Kubernetes :: ReplicaSet


A ReplicaSet might then dynamically drive the cluster back to the desired state via the creation of new Pods to keep your application running.

Consider an image-processing backend with 3 replicas. Those replicas are exchangeable; the front-end system should not care about backend replicas or even if a Pod is lost and recreated. Each Pod in a cluster has a unique IP address, even Pods on the same Node, so there needs to be a way of automatically reconciling changes among Pods so that your applications continue to function.

Replicas: 4 desired | 4 updated | 4 total | 4 available | 0 unavailable


Name Value
name ReplicaSet
stereotype null
visibility public
isAbstract false
isFinalSpecialization false
isLeaf false


Owned Elements