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 Autoscaler operator autoscales the database storage using
The following diagram shows how KubeDB Autoscaler operator autoscales the resources of
Redis database components. Open the image in a new tab to see the enlarged version.
The Auto Scaling process consists of the following steps:
At first, a user creates a
Redis Custom Resource (CR).
KubeDB Provisioner operator watches the
When the operator finds a
Redis CR, it creates required number of
StatefulSets and related necessary stuff like secrets, services, etc.
Each StatefulSet creates a Persistent Volume according to the Volume Claim Template provided in the statefulset configuration.
Then, in order to set up storage autoscaling of the various components (ie. ReplicaSet, Shard, ConfigServer etc.) of the
Redis database the user creates a
RedisAutoscaler CRO with desired configuration.
KubeDB Autoscaler operator watches the
KubeDB Autoscaler operator continuously watches persistent volumes of the databases to check if it exceeds the specified usage threshold.
If the usage exceeds the specified usage threshold, then
KubeDB Autoscaler operator creates a
RedisOpsRequest to expand the storage of the database.
KubeDB Ops-manager operator watches the
KubeDB Ops-manager operator will expand the storage of the database component as specified on the
In the next docs, we are going to show a step-by-step guide on Autoscaling storage of various Redis database components using