Fix rolling update deadlock with pod anti-affinity
maxSurge:1 + maxUnavailable:0 deadlocks with anti-affinity since there's no free physical host for the surge pod. Switch to maxSurge:0 + maxUnavailable:1 to terminate one old pod first.
This commit is contained in:
parent
a743787ce8
commit
7b0208408a
1 changed files with 2 additions and 2 deletions
|
|
@ -9,8 +9,8 @@ spec:
|
|||
strategy:
|
||||
type: RollingUpdate
|
||||
rollingUpdate:
|
||||
maxSurge: 1
|
||||
maxUnavailable: 0
|
||||
maxSurge: 0
|
||||
maxUnavailable: 1
|
||||
selector:
|
||||
matchLabels:
|
||||
app: prop
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue