New to KubeDB? Please start here.
Reconfiguring TLS of MongoDB Database
This guide will give an overview on how KubeDB Ops-manager operator reconfigures TLS configuration i.e. add TLS, remove TLS, update issuer/cluster issuer or Certificates and rotate the certificates of a MongoDB
database.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Reconfiguring MongoDB TLS Configuration Process Works
The following diagram shows how KubeDB Ops-manager operator reconfigures TLS of a MongoDB
database. Open the image in a new tab to see the enlarged version.
The Reconfiguring MongoDB TLS process consists of the following steps:
At first, a user creates a
MongoDB
Custom Resource Object (CRO).KubeDB
Provisioner operator watches theMongoDB
CRO.When the operator finds a
MongoDB
CR, it creates required number ofPetSets
and related necessary stuff like secrets, services, etc.Then, in order to reconfigure the TLS configuration of the
MongoDB
database the user creates aMongoDBOpsRequest
CR with desired information.KubeDB
Ops-manager operator watches theMongoDBOpsRequest
CR.When it finds a
MongoDBOpsRequest
CR, it pauses theMongoDB
object which is referred from theMongoDBOpsRequest
. So, theKubeDB
Provisioner operator doesn’t perform any operations on theMongoDB
object during the reconfiguring TLS process.Then the
KubeDB
Ops-manager operator will add, remove, update or rotate TLS configuration based on the Ops Request yaml.Then the
KubeDB
Ops-manager operator will restart all the Pods of the database so that they restart with the new TLS configuration defined in theMongoDBOpsRequest
CR.After the successful reconfiguring of the
MongoDB
TLS, theKubeDB
Ops-manager operator resumes theMongoDB
object so that theKubeDB
Provisioner operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on reconfiguring TLS configuration of a MongoDB database using MongoDBOpsRequest
CRD.