What is Rolling Update?
A Kubernetes deployment strategy that gradually replaces old pods with new ones.
A Rolling Update is the default Deployment update strategy in Kubernetes. It gradually replaces old pods with new pods, ensuring zero downtime. Controlled by maxSurge (extra pods above desired count during update) and maxUnavailable (pods that can be unavailable during update). New pods must pass readiness probes before old pods are terminated. If the new version is bad, kubectl rollout undo reverses the update by scaling back to the previous ReplicaSet.
Related Terms
More Kubernetes Terms
Admission Controller
A Kubernetes plugin that intercepts API requests before objects are persisted.
Auto Scaling
Automatically adjusting the number of compute resources based on demand.
ClusterIP
The default Kubernetes Service type that exposes a service on an internal cluster IP.
ConfigMap
A Kubernetes object for storing non-sensitive configuration data as key-value pairs.
Controller Manager
Kubernetes control plane component running control loops to maintain desired state.
CoreDNS
The default DNS server in Kubernetes clusters for service discovery.
Test your knowledge of Rolling Update and 130 other DevOps concepts