DevOps Intermediate

What is Rolling Update?

A deployment strategy that gradually replaces old application instances with new ones, maintaining availability throughout.

Rolling updates replace instances one at a time (or in small batches). At any point during the update, some instances run the old version and some run the new version. This ensures zero downtime but requires backward compatibility.

Kubernetes performs rolling updates by default: it creates new pods, waits for them to be ready, then terminates old pods. Parameters include maxSurge (extra pods during update) and maxUnavailable (pods that can be down simultaneously).

Related Terms

Infrastructure as Code (IaC)

The practice of managing infrastructure through machine-readable configuration files rather than manual processes.

Log Aggregation

The process of collecting, centralizing, and indexing log data from multiple sources for unified search and analysis.

The ability to understand a system's internal state from its external outputs through metrics, logs, and traces.

An open-source service mesh that provides traffic management, security, and observability for microservices on Kubernetes.

The practice of collecting, analyzing, and alerting on system metrics and logs to ensure application health and performance.

An endpoint or mechanism that reports whether an application is running correctly and ready to handle requests.

View All DevOps Terms →