This is an Enterprise-only feature. Please install KubeDB Enterprise Edition to try this feature.
New to KubeDB? Please start here.
This guide will give an overview on how KubeDB Autoscaler operator autoscales the database compute resources i.e. cpu and memory using
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 Object (CRO).
KubeDB Community operator watches the
When the operator finds a
MongoDB CRO, it creates required number of
StatefulSets and related necessary stuff like secrets, services, etc.
Then, in order to set up autoscaling of the various components (ie. ReplicaSet, Shard, ConfigServer, Mongos, etc.) of the
MongoDB database the user creates a
MongoDBAutoscaler CRO with desired configuration.
KubeDB Autoscaler operator watches the
KubeDB Autoscaler operator creates required number of Vertical Pod Autoscaler VPA for different components of the database, as specified in the
KubeDB Autoscaler operator continuously watches the VPA objects for recommendation.
If the VPA generated recommendation doesn’t match the current resources of the database, then
KubeDB Autoscaler operator creates a
MongoDBOpsRequest CRO to scale the database to match the recommendation provided by the VPA object.
KubeDB Enterprise operator watches the
KubeDB Enterprise operator will scale the database component vertically as specified on the
In the next docs, we are going to show a step by step guide on Autoscaling of various MongoDB database components using