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.
MariaDB Volume Expansion
This guide will give an overview on how KubeDB Ops Manager expand the volume of MariaDB
.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Volume Expansion Process Works
The following diagram shows how KubeDB Ops Manager expand the volumes of MariaDB
database components. Open the image in a new tab to see the enlarged version.
The Volume Expansion process consists of the following steps:
At first, a user creates a
MariaDB
Custom Resource (CR).KubeDB
Community operator watches theMariaDB
CR.When the operator finds a
MariaDB
CR, it creates requiredStatefulSet
and related necessary stuff like secrets, services, etc.The statefulSet creates Persistent Volumes 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 expand the volume of the
MariaDB
database the user creates aMariaDBOpsRequest
CR with desired information.KubeDB
Enterprise operator watches theMariaDBOpsRequest
CR.When it finds a
MariaDBOpsRequest
CR, it pauses theMariaDB
object which is referred from theMariaDBOpsRequest
. So, theKubeDB
Community operator doesn’t perform any operations on theMariaDB
object during the volume expansion process.Then the
KubeDB
Enterprise operator will expand the persistent volume to reach the expected size defined in theMariaDBOpsRequest
CR.After the successfully expansion of the volume of the related StatefulSet Pods, the
KubeDB
Enterprise operator updates the new volume size in theMariaDB
object to reflect the updated state.After the successful Volume Expansion of the
MariaDB
, theKubeDB
Enterprise operator resumes theMariaDB
object so that theKubeDB
Community operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on Volume Expansion of various MariaDB database using MariaDBOpsRequest
CRD.