You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
New to KubeDB? Please start here.
This guide will give you an overview on how KubeDB Enterprise operator replaces sentinel of a Redis instance.
KubeDB
concepts:The following diagram shows how KubeDB Enterprise operator replaces sentinel of Redis
. Open the image in a new tab to see the enlarged version.
The replace sentinel process consists of the following steps:
At first, a user creates Redis
and RedisSentinel
Custom Resource (CR).
KubeDB
Community operator watches the Redis
and RedisSentinel
CR.
When the operator finds a Redis
CR, it creates a StatefulSet
and related necessary stuff like appbinding, services, etc.
When the operator finds a RedisSentinel
CR, it creates a StatefulSet
and related necessary stuff like appbinding, services, etc.
Then, in order to replace the sentinel of the Redis
database the user creates a new RedisSentinel
object which will replace the old one and RedisOpsRequest
CR with reference to the newly created sentinel.
KubeDB
Enterprise operator watches the RedisOpsRequest
CR.
When it finds a RedisOpsRequest
CR, it pauses the Redis
object which is referred from the RedisOpsRequest
. So, the KubeDB
Community operator doesn’t perform any operations on the Redis
object during the upgrading process.
By looking at the target sentinel reference from RedisOpsRequest
CR, KubeDB
Enterprise operator removes current sentinel and add desired sentinel to the Redis
object. Then it may delete the old RedisSentinel
object if it is orphaned and user requested to remove it.
After successfully updating Redis
object, the KubeDB
Enterprise operator resumes the Redis
object so that the KubeDB
Community operator can resume its usual operations.
In the next docs, we are going to show a step-by-step guide on replacing sentinel of Redis database components using RedisOpsRequest
CRD.