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.

Redis Horizontal Scaling

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.

Before You Begin

How Horizontal Scaling Process Works

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.

  Horizontal scaling process of MongoDB
Fig: Horizontal scaling process of MongoDB

The Horizontal scaling process consists of the following steps:

  1. At first, a user creates a Redis Custom Resource (CR).

  2. KubeDB Community operator watches the Redis CR.

  3. When the operator finds a Redis CR, it creates required number of StatefulSets and related necessary stuff like secrets, services, appbindings, etc.

  4. 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.

  5. KubeDB Enterprise operator watches the RedisOpsRequest CR.

  6. 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.

  7. KubeDB Enterprise operator will watch the Redis object, continuously checking if the Redis cluster has been configured as described in the RedisOpsRequest.

  8. After 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 RedisOpsRequest CRD.