New to KubeDB? Please start here.
Ignite Volume Expansion
This guide will give an overview on how KubeDB Ops-manager operator expand the volume of Ignite
cluster nodes.
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 operator expand the volumes of Ignite
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
Ignite
Custom Resource (CR).KubeDB
Provisioner operator watches theIgnite
CR.When the operator finds a
Ignite
CR, it creates required number ofStatefulSets
and related necessary stuff like secrets, services, etc.Each StatefulSet creates a Persistent Volume 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 the
Ignite
database the user creates aIgniteOpsRequest
CR with desired information.KubeDB
Ops-manager operator watches theIgniteOpsRequest
CR.When it finds a
IgniteOpsRequest
CR, it halts theIgnite
object which is referred from theIgniteOpsRequest
. So, theKubeDB
Provisioner operator doesn’t perform any operations on theIgnite
object during the volume expansion process.Then the
KubeDB
Ops-manager operator will expand the persistent volume to reach the expected size defined in theIgniteOpsRequest
CR.After the successful Volume Expansion of the related StatefulSet Pods, the
KubeDB
Ops-manager operator updates the new volume size in theIgnite
object to reflect the updated state.After the successful Volume Expansion of the
Ignite
components, theKubeDB
Ops-manager operator resumes theIgnite
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 Ignite database components using IgniteOpsRequest
CRD.