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 Enterprise operator reconfigures TLS configuration i.e. add TLS, remove TLS, update issuer/cluster issuer or Certificates and rotate the certificates of a MariaDB
database.
KubeDB
concepts:The following diagram shows how KubeDB Enterprise operator reconfigures TLS of a MariaDB
database. Open the image in a new tab to see the enlarged version.
The Reconfiguring MariaDB TLS process consists of the following steps:
At first, a user creates a MariaDB
Custom Resource Object (CRO).
KubeDB
Community operator watches the MariaDB
CRO.
When the operator finds a MariaDB
CR, it creates required number of StatefulSets
and related necessary stuff like secrets, services, etc.
Then, in order to reconfigure the TLS configuration of the MariaDB
database the user creates a MariaDBOpsRequest
CR with desired information.
KubeDB
Enterprise operator watches the MariaDBOpsRequest
CR.
When it finds a MariaDBOpsRequest
CR, it pauses the MariaDB
object which is referred from the MariaDBOpsRequest
. So, the KubeDB
Community operator doesn’t perform any operations on the MariaDB
object during the reconfiguring TLS process.
Then the KubeDB
Enterprise operator will add, remove, update or rotate TLS configuration based on the Ops Request yaml.
Then the KubeDB
Enterprise operator will restart all the Pods of the database so that they restart with the new TLS configuration defined in the MariaDBOpsRequest
CR.
After the successful reconfiguring of the MariaDB
TLS, the KubeDB
Enterprise operator resumes the MariaDB
object so that the KubeDB
Community 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 MariaDB database using MariaDBOpsRequest
CRD.