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 Ops-manager operator updates the resources(for example CPU and Memory etc.) of the MongoDB
database.
KubeDB
concepts:The following diagram shows how KubeDB Ops-manager operator updates the resources of the MongoDB
database. Open the image in a new tab to see the enlarged version.
The vertical 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 update the resources(for example CPU
, Memory
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 vertical scaling process.
Then the KubeDB
Ops-manager operator will update resources of the StatefulSet Pods to reach desired state.
After the successful update of the resources of the StatefulSet’s replica, the KubeDB
Ops-manager operator updates the MongoDB
object to reflect the updated state.
After the successful update of the MongoDB
resources, 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 updating resources of MongoDB database using MongoDBOpsRequest
CRD.