-
Notifications
You must be signed in to change notification settings - Fork 16
Design and infrastructure
Andrei Dobre edited this page Dec 1, 2020
·
33 revisions
The operator supports rolling updates. A rolling restart is applyed to each leader-follower group one my one, always in ascending order of the leader-number.
The following steps are done by the RedisCluster controller during an update, sequentially for each leader:
- Recreate the follower pods of a leader using the new Redis image
- Wait until data sync between followers and leader is complete
- Update the leader
- Do a
FAILOVER
operation on one of the followers so it is promoted as new leader - Recreate the leader pod and add it as a follower of the node promoted during the previous step
- Wait for data sync
- Do a
FAILOVER
operation on the updated leader
- Do a
MaxSurge
and MaxUnavailable
options are currently not supported.