liveBook · Manning

ReplicaSet

As explained in Platform Engineering on Kubernetes

A ReplicaSet is a Kubernetes resource controller that maintains a specified number of matching pod instances.

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

How Platform Engineering on Kubernetes covers it

How deep it goes
Explains desired replica counts, automatic replacement, scaling commands, and single-replica downtime, but defers direct ReplicaSet management.
Examples
Demonstrates Frontend scaling, Pod deletion, automatic replacement, replica inspection, and HTTP 503 downtime.
What it assumes
Assumes familiarity with Kubernetes Deployments, Pods, services, and kubectl while illustrating replica behavior through the Frontend application.
What you can do after
Operate ReplicaSet behavior through kubectl by inspecting, scaling, and testing Pod recovery under failure.
How it connects
Connects ReplicaSets to Kubernetes Deployments, Pods, rolling updates, scaling, and Ingress controllers.

Also explained in

Compare how 5 books explain ReplicaSet →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Platform Engineering on Kubernetes. The section links point to the parts of the book it draws on.