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.
Reconfiguring MySQL
This guide will give an overview on how KubeDB Enterprise operator reconfigures MySQL
.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Reconfiguring MySQL Process Works
The following diagram shows how KubeDB Enterprise operator reconfigures MySQL
database components. Open the image in a new tab to see the enlarged version.
![Reconfiguring process of MySQL](/docs/v2023.08.18/guides/mysql/reconfigure/overview/reconfigure.jpg)
The Reconfiguring MySQL process consists of the following steps:
At first, a user creates a
MySQL
Custom Resource (CR).KubeDB
Community operator watches theMySQL
CR.When the operator finds a
MySQL
CR, it creates required number ofStatefulSets
and related necessary stuff like secrets, services, etc.Then, in order to reconfigure the
MySQL
standalone or cluster the user creates aMySQLOpsRequest
CR with desired information.KubeDB
Enterprise operator watches theMySQLOpsRequest
CR.When it finds a
MySQLOpsRequest
CR, it halts theMySQL
object which is referred from theMySQLOpsRequest
. So, theKubeDB
Community operator doesn’t perform any operations on theMySQL
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 theMySQLOpsRequest
CR.Then the
KubeDB
Enterprise operator will restart the related StatefulSet Pods so that they restart with the new configuration defined in theMySQLOpsRequest
CR.After the successful reconfiguring of the
MySQL
, theKubeDB
Enterprise operator resumes theMySQL
object so that theKubeDB
Community operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on reconfiguring MySQL database components using MySQLOpsRequest
CRD.