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 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
- You should be familiar with the following
KubeDB
concepts:
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.
The vertical scaling process consists of the following steps:
At first, a user creates a
Redis
Custom Resource (CR).KubeDB
Community operator watches theRedis
CR.When the operator finds a
Redis
CR, it creates required number ofStatefulSets
and related necessary stuff like appbinding, services, etc.Then, in order to update the resources(for example
CPU
,Memory
etc.) of theRedis
database the user creates aRedisOpsRequest
CR with desired information.KubeDB
Enterprise operator watches theRedisOpsRequest
CR.When it finds a
RedisOpsRequest
CR, it halts theRedis
object which is referred from theRedisOpsRequest
. So, theKubeDB
Community operator doesn’t perform any operations on theRedis
object during the vertical scaling process.Then the
KubeDB
Enterprise operator will update resources of the StatefulSet Pods to reach desired state.After the successful update of the resources of the StatefulSet’s replica, the
KubeDB
Enterprise operator updates theRedis
object to reflect the updated state.After the successful update of the
Redis
resources, theKubeDB
Enterprise operator resumes theRedis
object so that theKubeDB
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.