replica
One of several identical copies of a service or database running at the same time.
In more detail
Running replicas spreads load and lets one copy fail or be replaced while the others keep serving. In Kubernetes, the replica count says how many identical Pods should run, and a controller creates or deletes Pods to keep that number. A rolling update replaces replicas a few at a time.
Example
In the course lab, database replicas still used a credential that deployment seven revoked, so that deployment failed.Related terms
- Deployment — The Kubernetes object that keeps a chosen number of identical pods running and replaces them gradually when you change their template.
- configuration drift — The slow, unrecorded way machines end up with different versions and settings from each other.
- rolling update — Replacing instances of an application with the new version a few at a time while the rest keep serving.
- horizontal scaling — Handling more load by running more copies of a process, often on more machines, rather than making one machine bigger.
Taught in
- Drift Detection and Self-Healing — Continuous Integration & Continuous Delivery Pipelines
- Repository Layout for Environments — Continuous Integration & Continuous Delivery Pipelines
- Restoration: Failed Deployment Recovery Time — DevOps & Site Reliability Engineering
- Deployment Strategies: Rolling Updates — DevOps & Site Reliability Engineering