See how Kubernetes handles deployment rollouts. Simulate rolling updates with maxSurge and maxUnavailable settings. Understand how failed deployments are detected and rolled back.
Rolling updates
Kubernetes gradually replaces old pods with new ones. maxSurge controls how many extra pods can be created; maxUnavailable controls how many pods can be down during the update.
Rollback strategies
If readiness probes fail, the rollout pauses. You can manually rollback to a previous revision, or configure automatic rollback based on metrics with tools like Argo Rollouts.
Good for
- Understanding deployment strategies
- Configuring rollout parameters
- Planning production deployments
- SRE training
Questions people ask
What is the difference between maxSurge and maxUnavailable?
maxSurge allows creating extra pods above the desired count during updates. maxUnavailable allows removing pods below the desired count. Both can be absolute numbers or percentages.
When should I use blue-green vs canary?
Blue-green is simpler and offers instant rollback but requires double resources. Canary is better for gradual validation with real traffic but requires more sophisticated traffic management.