Rolling Updates
The rollingUpdate
option expects the Kubernetes configuration for rolling updates.
rollingUpdate: enabled: true maxSurge: "100%" maxUnavailable: "50%"
For Deployments
The following fields are supported for Deployments (none of the containers mounts any persistent volumes):
enabled
maxSurge
maxUnavailable
Example: Enabling Rolling Updates for Deployments
containers:- image: john/appbackendrollingUpdate: enabled: true maxSurge: "100%" maxUnavailable: "50%"
enabled
The enabled
option expects a boolean and defines if rolling updates should be enabled or disabled.
enabled
Default Value For enabled: false
info
If enabled = true
, the Kubernetes rolling update type will be set to RollingUpdate
(default: Recreate
).
maxSurge
The maxSurge
option expects a string defining a percentage of pods that can be created above the desired number of replicas.
maxSurge
Default Value For maxSurge: "25%"
maxUnavailable
The maxUnavailable
option expects a string defining a percentage of pods that can be unavailable during an update.
maxUnavailable
Default Value For maxUnavailable: "0%"
For StateFulSets
The following fields are supported for StatefulSets (at least one of the containers mounts a persistent volume):
enabled
partition
enabled
The enabled
option expects a boolean and defines if rolling updates should be enabled or disabled.
enabled
Default Value For enabled: false
info
If enabled = true
, the Kubernetes rolling update type will be set to RollingUpdate
(default: Recreate
).
partition
The partition
option expects an integer that tells Kubernetes to only update pods with an ordinal number greater than or equal this value.
partition
Default Value For partition: 1