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 mongodbautoscaler
crd.
KubeDB
concepts:The following diagram shows how KubeDB Autoscaler operator autoscales the resources of MongoDB
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 MongoDB
Custom Resource (CR).
KubeDB
Provisioner operator watches the MongoDB
CR.
When the operator finds a MongoDB
CR, it creates required number of StatefulSets
and related necessary stuff like secrets, services, etc.
Then, in order to set up storage autoscaling of the various components (ie. ReplicaSet, Shard, ConfigServer etc.) of the MongoDB
database the user creates a MongoDBAutoscaler
CRO with desired configuration.
KubeDB
Autoscaler operator watches the MongoDBAutoscaler
CRO.
KubeDB
Autoscaler operator continuously watches persistent volumes of the databases to check if it exceeds the specified usage threshold.
KubeDB
Autoscaler operator creates a MongoDBOpsRequest
to expand the storage of the database.KubeDB
Ops-manager operator watches the MongoDBOpsRequest
CRO.
Then the KubeDB
Ops-manager operator will expand the storage of the database component as specified on the MongoDBOpsRequest
CRO.
In the next docs, we are going to show a step by step guide on Autoscaling storage of various MongoDB database components using MongoDBAutoscaler
CRD.