New to KubeDB? Please start here.

MariaDB Compute Resource Autoscaling

This guide will give an overview on how KubeDB Autoscaler operator autoscales the database compute resources i.e. cpu and memory using mariadbautoscaler crd.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • MariaDB
  • MariaDBAutoscaler
  • MariaDBOpsRequest

How Compute Autoscaling Works

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:

1. At first, the user creates a MariaDB Custom Resource Object (CRO).

2. KubeDB Community operator watches the MariaDB CRO.

3. When the operator finds a MariaDB CRO, it creates required number of StatefulSets and related necessary stuff like secrets, services, etc.

4. Then, in order to set up autoscaling of the CPU & Memory resources of the MariaDB database the user creates a MariaDBAutoscaler CRO with desired configuration.

5. KubeDB Autoscaler operator watches the MariaDBAutoscaler CRO.

6. KubeDB Autoscaler operator utilizes the modified version of Kubernetes official VPA-Recommender for different components of the database, as specified in the mariadbautoscaler CRO. It generates recommendations based on resource usages, & store them in the status section of the autoscaler CRO.

7. If the generated recommendation doesn’t match the current resources of the database, then KubeDB Autoscaler operator creates a MariaDBOpsRequest CRO to scale the database to match the recommendation provided by the VPA object.

8. KubeDB Ops-Manager operator watches the MariaDBOpsRequest CRO.

9. Lastly, the KubeDB Ops-Manager operator will scale the database component vertically as specified on the MariaDBOpsRequest CRO.

In the next docs, we are going to show a step by step guide on Autoscaling of MariaDB database using MariaDBAutoscaler CRD.