New to KubeDB? Please start here.

Reconfiguring MongoDB

This guide will give an overview on how KubeDB Ops-manager operator reconfigures MongoDB database components such as ReplicaSet, Shard, ConfigServer, Mongos, etc.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • MongoDB
  • MongoDBOpsRequest

How Reconfiguring MongoDB Process Works

The following diagram shows how KubeDB Ops-manager operator reconfigures MongoDB database components. Open the image in a new tab to see the enlarged version.

  

The Reconfiguring MongoDB process consists of the following steps:

1. At first, a user creates a MongoDB Custom Resource (CR).

2. KubeDB Provisioner operator watches the MongoDB CR.

3. When the operator finds a MongoDB CR, it creates required number of PetSets and related necessary stuff like secrets, services, etc.

4. Then, in order to reconfigure the various components (ie. ReplicaSet, Shard, ConfigServer, Mongos, etc.) of the MongoDB database the user creates a MongoDBOpsRequest CR with desired information.

5. KubeDB Ops-manager operator watches the MongoDBOpsRequest CR.

6. 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 reconfiguring process.

7. Then the KubeDB Ops-manager operator will replace the existing configuration with the new configuration provided or merge the new configuration with the existing configuration according to the MongoDBOpsRequest CR.

8. Then the KubeDB Ops-manager operator will restart the related PetSet Pods so that they restart with the new configuration defined in the MongoDBOpsRequest CR.

9. After the successful reconfiguring of the MongoDB components, 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 reconfiguring MongoDB database components using MongoDBOpsRequest CRD.