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 an overview on how KubeDB Enterprise operator scales up or down of
Redis cluster database for both the number of replicas and masters.
The following diagram shows how KubeDB Enterprise operator scales up or down
Redis database components. Open the image in a new tab to see the enlarged version.
The Horizontal scaling process consists of the following steps:
At first, a user creates a
Redis Custom Resource (CR).
KubeDB Community operator watches the
When the operator finds a
Redis CR, it creates required number of
StatefulSets and related necessary stuff like secrets, services, appbindings, etc.
Then, in order to scale the number of replica or master for the
Redis cluster database the user creates a
RedisOpsRequest CR with desired information.
KubeDB Enterprise operator watches the
When it finds a
RedisOpsRequest CR, it patches the
Redis object which is referred from the
RedisOpsRequest. After that, the
KubeDB Community operator tries to reconcile the state of the
Redis object during the horizontal scaling process.
KubeDB Enterprise operator will watch the
Redis object, continuously checking if the
Redis cluster has been configured as described in the
Redis cluster is configured as desired,
KubeDB Enterprise operator will declare the OpsRequest as successful.
In the next docs, we are going to show a step by step guide on horizontal scaling of Redis database using