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 MariaDB
.
KubeDB
concepts:The following diagram shows how KubeDB Enterprise operator reconfigures MariaDB
database components. Open the image in a new tab to see the enlarged version.
The Reconfiguring MariaDB process consists of the following steps:
At first, a user creates a MariaDB
Custom Resource (CR).
KubeDB
Community operator watches the MariaDB
CR.
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 MariaDB
standalone or cluster the user creates a MariaDBOpsRequest
CR with desired information.
KubeDB
Enterprise operator watches the MariaDBOpsRequest
CR.
When it finds a MariaDBOpsRequest
CR, it halts 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 process.
Then the KubeDB
Enterprise operator will replace the existing configuration with the new configuration provided or merge the new configuration with the existing configuration according to the MariaDBOpsRequest
CR.
Then the KubeDB
Enterprise operator will restart the related StatefulSet Pods so that they restart with the new configuration defined in the MariaDBOpsRequest
CR.
After the successful reconfiguring of the MariaDB
, 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 MariaDB database components using MariaDBOpsRequest
CRD.