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 Vertical Autoscaling
This guide will give an overview on how KubeDB Autoscaler operator autoscales the database storage using mysqlautoscaler
crd.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Storage 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.
![Storage Autoscaling process of MySQL](/docs/v2023.08.18/guides/mysql/autoscaler/storage/overview/images/storage-autoscaling.jpg)
The Auto Scaling process consists of the following steps:
At first, a user creates a
MySQL
Custom Resource (CR).KubeDB
Community operator watches theMySQL
CR.When the operator finds a
MySQL
CR, it creates required number ofStatefulSets
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
MySQL
database the user creates aMySQLAutoscaler
CRO with desired configuration.KubeDB
Autoscaler operator watches theMySQLAutoscaler
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 aMySQLOpsRequest
to expand the storage of the database.KubeDB
Enterprise operator watches theMySQLOpsRequest
CRO.Then the
KubeDB
Enterprise operator will expand the storage of the database component as specified on theMySQLOpsRequest
CRO.
In the next docs, we are going to show a step by step guide on Autoscaling storage of various MySQL database components using MySQLAutoscaler
CRD.