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 you an overview of how KubeDB enterprise operator updates the resources(for example Memory and RAM etc.) of the MySQL
database server.
KubeDB
concepts:The following diagram shows how the KubeDB enterprise operator used to update the resources of the MySQL
database server. Open the image in a new tab to see the enlarged version.
The vertical scaling process consists of the following steps:
At first, a user creates a MySQL
cr.
KubeDB
community operator watches for the MySQL
cr.
When it finds one, it creates a StatefulSet
and related necessary stuff like secret, service, etc.
Then, in order to update the resources(for example CPU
, Memory
etc.) of the MySQL
database the user creates a MySQLOpsRequest
cr.
KubeDB
enterprise operator watches for MySQLOpsRequest
.
When it finds one, it halts the MySQL
object so that the KubeDB
community operator doesn’t perform any operation on the MySQL
during the scaling process.
Then the KubeDB
enterprise operator will update resources of the StatefulSet replicas to reach the desired state.
After successful updating of the resources of the StatefulSet’s replica, the KubeDB
enterprise operator updates the MySQL
object resources to reflect the updated state.
After successful updating of the MySQL
resources, the KubeDB
enterprise operator resumes the MySQL
object so that the KubeDB
community operator resumes its usual operations.
In the next doc, we are going to show a step by step guide on updating resources of MySQL database using vertical scaling operation.