New to KubeDB? Please start here.

Redis Vertical Scaling Overview

This guide will give you an overview on how KubeDB Enterprise operator updates the resources(for example CPU and Memory etc.) of the Redis database.

Before You Begin

How Vertical Scaling Process Works

The following diagram shows how KubeDB Enterprise operator updates the resources of the Redis database. Open the image in a new tab to see the enlarged version.

  Vertical scaling process of MongoDB
Fig: Vertical scaling process of MongoDB

The vertical 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 appbinding, services, etc.

  4. Then, in order to update the resources(for example CPU, Memory etc.) of the Redis 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 halts 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 vertical scaling process.

  7. Then the KubeDB Enterprise operator will update resources of the StatefulSet Pods to reach desired state.

  8. After the successful update of the resources of the StatefulSet’s replica, the KubeDB Enterprise operator updates the Redis object to reflect the updated state.

  9. After the successful update of the Redis resources, the KubeDB Enterprise operator resumes the Redis object so that the KubeDB Community operator resumes its usual operations.

In the next docs, we are going to show a step by step guide on updating resources of Redis database using RedisOpsRequest CRD.