You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
We use cookies and other similar technology to collect data to improve your experience on our site, as described in our Privacy Policy.
Run Production-Grade Databases on Kubernetes
Backup and Recovery Solution for Kubernetes
Run Production-Grade Vault on Kubernetes
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
KubeDB simplifies Provision, Upgrade, Scaling, Volume Expansion, Monitor, Backup, Restore for various Databases in Kubernetes on any Public & Private Cloud
A complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.
KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp's Vault on Kubernetes.
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
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 Community 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.
Each StatefulSet creates a Persistent Volume according to the Volume Claim Template provided in the statefulset configuration. This Persistent Volume will be expanded by the KubeDB Enterprise operator.
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.
If the usage exceeds the specified usage threshold, then KubeDB Autoscaler operator creates a MongoDBOpsRequest to expand the storage of the database.
KubeDB Enterprise operator watches the MongoDBOpsRequest CRO.
Then the KubeDB Enterprise 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.