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.
MySQL Replication Mode Transform
This guide will give an overview on how KubeDB Ops Manager transform replication mode of MySQL
. Currently, you can transform remote replica
to group replication
.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Replication Mode Transform Process Works
The following diagram shows how KubeDB Ops Manager transform replication mode of MySQL
database components. Open the image in a new tab to see the enlarged version.
The Replication Mode Transform process consists of the following steps:
At first, a user creates a
MySQL
Custom Resource (CR).KubeDB
provisioner operator watches theMySQL
CR.When the operator finds a
MySQL
CR, it creates requiredPetSet
and related necessary stuff like secrets, services, etc.Then, in order to transform replication mode of the
MySQL
database the user creates aMySQLOpsRequest
CR with desired information.KubeDB
ops-manager operator watches theMySQLOpsRequest
CR.When it finds a
MySQLOpsRequest
CR, it pauses theMySQL
object which is referred from theMySQLOpsRequest
. So, theKubeDB
provisioner operator doesn’t perform any operations on theMySQL
object during the mode transform process.Then the
KubeDB
ops-request operator will transform replication mode to reach the expected replication mode defined in theMySQLOpsRequest
CR.After the successful transformation of replication mode of the MySQL database, the
KubeDB
ops-request operator updates the new replication mode in theMySQL
object to reflect the updated state. After that, theKubeDB
ops-request operator resumes theMySQL
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 transform replication mode of various MySQL database using MySQLOpsRequest
CRD.