Update the app deployment in the abc namespace with a maxSurge of 5% and a maxUn . . .

Kubernetes
#1

Manas Sahoo:
Update the app deployment in the abc namespace with a maxSurge of 5% and a maxUnavailable of 2%
Perform a rolling update of the def deployment, changing the nginx image version to 1.13
Roll back the app deployment to the previous version

Is it required to mention type: rollingUpdate ???

spec:
strategy:
rollingUpdate:
maxSurge: 5
maxUnavailable: 2
type: rollingUpdate

#2

Dhawan Shringi:
Yes it is.

#3

chris resnik:
because without rolling update, you cannot have those features

#4

chris resnik:
fundamental connection

#5

Tanumoy Ghosh:
It should be type:RollingUpdate

#6

Manas Sahoo:
ok thanks Chris and Tanumoy

#7

Hi,

As the maxSurge and maxUnavailable is given in percentage(5% and 2%) in question, in yaml also it should be mentioned with % or only numbers.

#8

Hi @kodecloud2295,
maxUnavailable
The maximum number of pods that can be unavailable during the update. Value
can be an absolute number (ex: 5) or a percentage of desired pods (ex:
10%). Absolute number is calculated from percentage by rounding down. This
can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set
to 30%, the old ReplicaSet can be scaled down to 70% of desired pods
immediately when the rolling update starts. Once new pods are ready, old
ReplicaSet can be scaled down further, followed by scaling up the new
ReplicaSet, ensuring that the total number of pods available at all times
during the update is at least 70% of desired pods.

IntOrString is a type that can hold an int32 or a string. When used in JSON
or YAML marshalling and unmarshalling, it produces or consumes the inner
type. This allows you to have, for example, a JSON field that can accept a
name or number.

Thanks,
Trung.