New to KubeDB? Please start here.
This guide will give an overview on how KubeDB Ops Manager reconfigures PerconaXtraDB
.
KubeDB
concepts:The following diagram shows how KubeDB Ops Manager reconfigures PerconaXtraDB
database components. Open the image in a new tab to see the enlarged version.
The Reconfiguring PerconaXtraDB process consists of the following steps:
At first, a user creates a PerconaXtraDB
Custom Resource (CR).
KubeDB
Community operator watches the PerconaXtraDB
CR.
When the operator finds a PerconaXtraDB
CR, it creates required number of StatefulSets
and related necessary stuff like secrets, services, etc.
Then, in order to reconfigure the PerconaXtraDB
standalone or cluster the user creates a PerconaXtraDBOpsRequest
CR with desired information.
KubeDB
Enterprise operator watches the PerconaXtraDBOpsRequest
CR.
When it finds a PerconaXtraDBOpsRequest
CR, it halts the PerconaXtraDB
object which is referred from the PerconaXtraDBOpsRequest
. So, the KubeDB
Community operator doesn’t perform any operations on the PerconaXtraDB
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 PerconaXtraDBOpsRequest
CR.
Then the KubeDB
Enterprise operator will restart the related StatefulSet Pods so that they restart with the new configuration defined in the PerconaXtraDBOpsRequest
CR.
After the successful reconfiguring of the PerconaXtraDB
, the KubeDB
Enterprise operator resumes the PerconaXtraDB
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 PerconaXtraDB database components using PerconaXtraDBOpsRequest
CRD.