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 storage using mariadbautoscaler
crd.
KubeDB
concepts:The following diagram shows how KubeDB Autoscaler operator autoscales the resources of MariaDB
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, a user creates a MariaDB
Custom Resource (CR).
KubeDB
Community operator watches the MariaDB
CR.
When the operator finds a MariaDB
CR, it creates required number of StatefulSets
and related necessary stuff like secrets, services, etc.
Each StatefulSet creates a Persistent Volume according to the Volume Claim Template provided in the statefulset configuration. This Persistent Volume will be expanded by the KubeDB
Enterprise operator.
Then, in order to set up storage autoscaling of the MariaDB
database the user creates a MariaDBAutoscaler
CRO with desired configuration.
KubeDB
Autoscaler operator watches the MariaDBAutoscaler
CRO.
KubeDB
Autoscaler operator continuously watches persistent volumes of the databases to check if it exceeds the specified usage threshold.
If the usage exceeds the specified usage threshold, then KubeDB
Autoscaler operator creates a MariaDBOpsRequest
to expand the storage of the database.
KubeDB
Enterprise operator watches the MariaDBOpsRequest
CRO.
Then the KubeDB
Enterprise operator will expand the storage of the database component as specified on the MariaDBOpsRequest
CRO.
In the next docs, we are going to show a step by step guide on Autoscaling storage of various MariaDB database components using MariaDBAutoscaler
CRD.