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 expand the volume of MariaDB
.
KubeDB
concepts:The following diagram shows how KubeDB Enterprise operator 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 the MariaDB
CR.
When the operator finds a MariaDB
CR, it creates required StatefulSet
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 a MariaDBOpsRequest
CR with desired information.
KubeDB
Enterprise operator watches the MariaDBOpsRequest
CR.
When it finds a MariaDBOpsRequest
CR, it pauses 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 volume expansion process.
Then the KubeDB
Enterprise operator will expand the persistent volume to reach the expected size defined in the MariaDBOpsRequest
CR.
After the successfully expansion of the volume of the related StatefulSet Pods, the KubeDB
Enterprise operator updates the new volume size in the MariaDB
object to reflect the updated state.
After the successful Volume Expansion of the MariaDB
, 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 Volume Expansion of various MariaDB database using MariaDBOpsRequest
CRD.