rolling update
Replacing instances of an application with the new version a few at a time while the rest keep serving.
In more detail
It is the default strategy of a Kubernetes Deployment. maxSurge and maxUnavailable bound the extra and missing capacity, and readiness decides when the next replacement may begin. Old and new versions share traffic during the rollout.
Examples
both versions serve traffic at once, so the schema must accept bothstrategy:
type: RollingUpdate
rollingUpdate:
maxUnavailable: 0
maxSurge: 1Related terms
- replica — One of several identical copies of a service or database running at the same time.
- backward compatibility — The property that a new version of an interface still works for clients written against the old one.
- blue-green deployment — Running two complete environments, blue for the current release and green for the candidate, and switching traffic between them in one step.
- canary release — Sending a small share of real traffic to a new version first, and increasing it only while its metrics stay healthy.
- maxSurge — The rolling update setting for how many extra Pods may be created above the desired count during an update.
- maxUnavailable — The rolling update setting for how many Pods may be missing from the desired count during an update.
- readiness probe — A check that decides whether a pod should receive traffic right now; failing it removes the pod from its Service without restarting it.
- Deployment — The Kubernetes object that keeps a chosen number of identical pods running and replaces them gradually when you change their template.
- zero-downtime deployment — Releasing a new version while users keep being served, with no period where the service is unavailable.
- expand-and-contract — A way to change a live database in safe steps: add the new structure, move data and code to it, then remove the old structure.
- rolling restart — Replacing the processes or instances of a service one at a time, starting each new one before stopping an old one, so the service never goes down.
- headroom — Capacity kept free above the expected peak, so the system survives deployments, spikes and failures.
- cold cache — A cache that is empty or nearly empty, so almost every request misses and goes to the origin.
- rollback — Returning a system to a previous known-good version after a bad change.
Taught in
- Strategies Across Compute: The Canary That Saw Nothing — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Introduction to Release Strategies — Continuous Integration & Continuous Delivery Pipelines
- Rolling Updates and Rollbacks — Continuous Integration & Continuous Delivery Pipelines
- Design And Build: Timed Drill And Checkpoint — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Rolling Updates And Rollbacks — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Blue/Green With Labels And A Service — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Canary Releases From Replica Counts — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Kustomize Bases, Overlays And Patches — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Deployment: Timed Drill And Checkpoint — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Mock Exam: Sixteen Tasks Against The Clock — Certified Kubernetes Application Developer (CKAD) Exam Prep
- The Two A.M. Page — CompTIA Cloud+ (CV0-004) Exam Prep
- A Release That Cannot Take Checkout Down — CompTIA Cloud+ (CV0-004) Exam Prep
- Build, Release, Run And Processes — DevOps & Site Reliability Engineering
- Deployment Strategies: Rolling Updates — DevOps & Site Reliability Engineering
- Decoupling Release From Deployment: Feature Flags — DevOps & Site Reliability Engineering
- Database Access & Migrations: ORM & Data Layers — Production Full-Stack Engineering
- Bidirectional WebSockets: Reconnection & Heartbeats — Production Full-Stack Engineering
- Kubernetes Ingress, Routing & TLS Termination — Production Full-Stack Engineering
- Always A Way Back: Rolling, Blue/Green And Canary — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Delivery Sprint: Friday At Five — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Deployments, ReplicaSets, Rollouts And Rollback — Kubernetes: Production-Grade Container Orchestration
- Production Hardening: Graceful Shutdown & Docker — Node.js Internals & Backend Services
- Back Of The Envelope Estimation: Traffic And Throughput — Scalable System Design & Distributed Architecture
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture
References
- Kubernetes documentation: Deployments
- Kubernetes tutorial: performing a rolling update
- AWS whitepaper: Rolling deployments