Anish Nagaraj:
Hi all, Have any of you found an example for RollingUpdate, maxSurge, maxUnavailable on http://kubernetes.io|kubernetes.io documentation. Something like following:
replicas: 3
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 1
maxUnavailable: 0
Tharanath:
.spec.strategy.rollingUpdate.maxUnavailable
is an optional field that specifies the maximum number of Pods that can be unavailable during the update process.
Tharanath:
.spec.strategy.rollingUpdate.maxSurge
is an optional field that specifies the maximum number of Pods that can be created over the desired number of Pods.
Tharanath:
Rolling Update Deployment updates Pods in a rolling update fashion when .spec.strategy.type==RollingUpdate
. You can specify maxUnavailable
and maxSurge
to control the rolling update process.
Tharanath:
default value is 25% if not specified
Mike K:
I never found one for a deployment, but I did find one for a DaemonSet - https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/
Mike K:
I believe the RollingUpdate parts are like for like
Anish Nagaraj:
Thank you Tharanath and Mike. This is in deed useful