A ReplicaSet maintains a specified number of matching Pod instances. Deployments manage ReplicaSets in normal workflows, while ReplicaSets provide the replica count and recovery behavior behind scaling and rolling updates. section 2.3.3
Two Frontend replicas
With two Frontend replicas, one Pod can continue serving requests while Kubernetes recreates another that has failed. With only one replica, deleting the running Pod causes temporary unavailability and may produce an HTTP 503 until the replacement becomes ready. section 2.4.1




