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 scales up or down PerconaXtraDB Cluster
.
KubeDB
concepts:The following diagram shows how KubeDB Enterprise operator scales up or down PerconaXtraDB
database components. Open the image in a new tab to see the enlarged version.
The Horizontal scaling 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 scale the PerconaXtraDB
database the user creates a PerconaXtraDBOpsRequest
CR with desired information.
KubeDB
Enterprise operator watches the PerconaXtraDBOpsRequest
CR.
When it finds a PerconaXtraDBOpsRequest
CR, it pauses 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 horizontal scaling process.
Then the KubeDB
Enterprise operator will scale the related StatefulSet Pods to reach the expected number of replicas defined in the PerconaXtraDBOpsRequest
CR.
After the successfully scaling the replicas of the StatefulSet Pods, the KubeDB
Enterprise operator updates the number of replicas in the PerconaXtraDB
object to reflect the updated state.
After the successful scaling of the PerconaXtraDB
replicas, 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 horizontal scaling of PerconaXtraDB database using PerconaXtraDBOpsRequest
CRD.