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 Ops-manager operator scales up or down MongoDB
database replicas of various component such as ReplicaSet, Shard, ConfigServer, Mongos, etc.
KubeDB
concepts:
The following diagram shows how KubeDB Ops-manager operator scales up or down MongoDB
database components. Open the image in a new tab to see the enlarged version.
The Horizontal 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 scale the various components (ie. ReplicaSet, Shard, ConfigServer, Mongos, etc.) of the MongoDB
database the user creates a MongoDBOpsRequest
CR with desired information.
KubeDB
Ops-manager operator watches the MongoDBOpsRequest
CR.
When it finds a MongoDBOpsRequest
CR, it halts the MongoDB
object which is referred from the MongoDBOpsRequest
. So, the KubeDB
Provisioner operator doesn’t perform any operations on the MongoDB
object during the horizontal scaling process.
Then the KubeDB
Ops-manager operator will scale the related StatefulSet Pods to reach the expected number of replicas defined in the MongoDBOpsRequest
CR.
After the successfully scaling the replicas of the related StatefulSet Pods, the KubeDB
Ops-manager operator updates the number of replicas in the MongoDB
object to reflect the updated state.
After the successful scaling of the MongoDB
replicas, the KubeDB
Ops-manager operator resumes the MongoDB
object so that the KubeDB
Provisioner operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on horizontal scaling of MongoDB database using MongoDBOpsRequest
CRD.