Set maxSurge to 100%. Here's some info on what it implies.
The idea is to roll out newer versions as quickly as possible so that the period where a K8s service load balances requests between old and new versions during a rolling update is reduced. Note that there might be a case where the existing nodes don't have the capacity for all the new pods, as a result, it'll still take a while for the new pods to be ready. In any case, it shouldn't be worse than what we have right now.
All other changes (strategy.type and maxUnavailable) are set to their defaults.
Set
maxSurgeto100%. Here's some info on what it implies.The idea is to roll out newer versions as quickly as possible so that the period where a K8s service load balances requests between old and new versions during a rolling update is reduced. Note that there might be a case where the existing nodes don't have the capacity for all the new pods, as a result, it'll still take a while for the new pods to be ready. In any case, it shouldn't be worse than what we have right now.
All other changes (
strategy.typeandmaxUnavailable) are set to their defaults.