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.

MySQL 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 mysqlautoscaler crd.

Before You Begin

How Compute Autoscaling Works

The following diagram shows how KubeDB Autoscaler operator autoscales the resources of MySQL database components. Open the image in a new tab to see the enlarged version.

  Auto Scaling process of MySQL
Fig: Auto Scaling process of MySQL

The Auto Scaling process consists of the following steps:

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

  2. KubeDB Community operator watches the MySQL CRO.

  3. When the operator finds a MySQL 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 MySQL database the user creates a MySQLAutoscaler CRO with desired configuration.

  5. KubeDB Autoscaler operator watches the MySQLAutoscaler CRO.

  6. KubeDB Autoscaler operator utilizes the modified version of Kubernetes official VPA-Recommender for different components of the database, as specified in the mysqlautoscaler 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 MySQLOpsRequest CRO to scale the database to match the recommendation provided by the VPA object.

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

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

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