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 Autoscaler operator autoscales the database compute resources i.e. cpu and memory using perconaxtradbautoscaler
crd.
KubeDB
concepts:The following diagram shows how KubeDB Autoscaler operator autoscales the resources of PerconaXtraDB
database components. Open the image in a new tab to see the enlarged version.
The Auto Scaling process consists of the following steps:
At first, the user creates a PerconaXtraDB
Custom Resource Object (CRO).
KubeDB
Community operator watches the PerconaXtraDB
CRO.
When the operator finds a PerconaXtraDB
CRO, it creates required number of StatefulSets
and related necessary stuff like secrets, services, etc.
Then, in order to set up autoscaling of the CPU & Memory resources of the PerconaXtraDB
database the user creates a PerconaXtraDBAutoscaler
CRO with desired configuration.
KubeDB
Autoscaler operator watches the PerconaXtraDBAutoscaler
CRO.
KubeDB
Autoscaler operator utilizes the modified version of Kubernetes official VPA-Recommender for different components of the database, as specified in the perconaxtradbautoscaler
CRO.
It generates recommendations based on resource usages, & store them in the status
section of the autoscaler CRO.
If the generated recommendation doesn’t match the current resources of the database, then KubeDB
Autoscaler operator creates a PerconaXtraDBOpsRequest
CRO to scale the database to match the recommendation provided by the VPA object.
KubeDB Ops-Manager operator
watches the PerconaXtraDBOpsRequest
CRO.
Lastly, the KubeDB Ops-Manager operator
will scale the database component vertically as specified on the PerconaXtraDBOpsRequest
CRO.
In the next docs, we are going to show a step by step guide on Autoscaling of PerconaXtraDB database using PerconaXtraDBAutoscaler
CRD.