New to KubeDB? Please start here.
SingleStore Volume Expansion
This guide will give an overview on how KubeDB Ops Manager expand the volume of SingleStore
.
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 SingleStore
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
SingleStore
Custom Resource (CR).KubeDB
Provisioner operator watches theSingleStore
CR.When the operator finds a
SingleStore
CR, it creates requiredPetSet
and related necessary stuff like secrets, services, etc.The petSet creates Persistent Volumes according to the Volume Claim Template provided in the petset configuration. This Persistent Volume will be expanded by the
KubeDB
Ops-manager operator.Then, in order to expand the volume of the
SingleStore
database the user creates aSingleStoreOpsRequest
CR with desired information.KubeDB
Ops-manager operator watches theSingleStoreOpsRequest
CR.When it finds a
SingleStoreOpsRequest
CR, it pauses theSingleStore
object which is referred from theSingleStoreOpsRequest
. So, theKubeDB
Provisioner operator doesn’t perform any operations on theSingleStore
object during the volume expansion process.Then the
KubeDB
Ops-manager operator will expand the persistent volume to reach the expected size defined in theSingleStoreOpsRequest
CR.After the successfully expansion of the volume of the related PetSet Pods, the
KubeDB
Ops-manager operator updates the new volume size in theSingleStore
object to reflect the updated state.After the successful Volume Expansion of the
SingleStore
, theKubeDB
Ops-manager operator resumes theSingleStore
object so that theKubeDB
Provisioner operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on Volume Expansion of various SingleStore database using SingleStoreOpsRequest
CRD.