Skip to content

maxUnavailable parameter

The maxUnavailable parameter is a configuration field used within the Kubernetes Deployment strategy.^[400-devops-06-kubernetes-k8s-ithelp-day13-readme.md] It is specifically defined under spec.strategy.rollingUpdate as spec.strategy.rollingUpdate.maxUnavailable.^[400-devops-06-kubernetes-k8s-ithelp-day13-readme.md]

Function

This parameter specifies the maximum number of Pods that can be unavailable during the update process.^[400-devops-06-kubernetes-k8s-ithelp-day13-readme.md] It acts as a control mechanism for the update rate, determining the tolerance for service downtime while the system is performing a rolling update.^[400-devops-06-kubernetes-k8s-ithelp-day13-readme.md]

Usage

When configuring a [[RollingUpdate|Rolling Update]], maxUnavailable is used in conjunction with the maxSurge parameter to ensure stability during the deployment of a new version.^[400-devops-06-kubernetes-k8s-ithelp-day13-readme.md]

Sources

^[400-devops-06-kubernetes-k8s-ithelp-day13-readme.md]