While doing the Redis cluster in-service upgrade from older chart to newer chart. Redis operator is performing the Rolling update shard by shard which is fine.
but in one shard it is upgrading the master replicas at once due to which there is disconnection with the application.
can we improve the Rolling update logic such that first it upgrade the replicas of one shard then promote that replica to master and then we upgrade master and new master will join back as replica.?
While doing the Redis cluster in-service upgrade from older chart to newer chart. Redis operator is performing the Rolling update shard by shard which is fine. but in one shard it is upgrading the master replicas at once due to which there is disconnection with the application.
can we improve the Rolling update logic such that first it upgrade the replicas of one shard then promote that replica to master and then we upgrade master and new master will join back as replica.?