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 Enterprise operator vertically scales up MariaDB
.
KubeDB
concepts:The following diagram shows how KubeDB Enterprise operator scales up or down MariaDB
database components. 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 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.
Then, in order to update the resources(for example CPU
, Memory
etc.) of the MariaDB
database the user creates a MariaDBOpsRequest
CR with desired information.
KubeDB
Enterprise operator watches the MariaDBOpsRequest
CR.
When it finds a MariaDBOpsRequest
CR, it halts the MariaDB
object which is referred from the MariaDBOpsRequest
. So, the KubeDB
Community operator doesn’t perform any operations on the MariaDB
object during the vertical scaling process.
Then the KubeDB
Enterprise operator will update resources of the StatefulSet Pods to reach desired state.
After the successful update of the resources of the StatefulSet’s replica, the KubeDB
Enterprise operator updates the MariaDB
object to reflect the updated state.
After the successful update of the MariaDB
resources, the KubeDB
Enterprise operator resumes the MariaDB
object so that the KubeDB
Community operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on updating resources of MariaDB database using MariaDBOpsRequest
CRD.