Hi all, Have any of you found an example for RollingUpdate, maxSurge, maxUnavail . . .

Kubernetes
#1

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
#2

Tharanath:
.spec.strategy.rollingUpdate.maxUnavailable is an optional field that specifies the maximum number of Pods that can be unavailable during the update process.

#3

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.

#4

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.

#5

Tharanath:
default value is 25% if not specified

#6

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/

#7

Mike K:
I believe the RollingUpdate parts are like for like

#8

Anish Nagaraj:
Thank you Tharanath and Mike. This is in deed useful