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
The following diagram shows how KubeDB Enterprise operator 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
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
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.
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
KubeDB Enterprise operator will restart the related StatefulSet Pods so that they restart with the new configuration defined in the
After the successful reconfiguring of 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