New to KubeDB? Please start here.
RabbitMQ Volume Expansion
This guide will give an overview on how KubeDB Ops-manager operator expand the volume of RabbitMQ cluster nodes.
Before You Begin
- You should be familiar with the following
KubeDBconcepts:
How Volume Expansion Process Works
The following diagram shows how KubeDB Ops-manager operator expand the volumes of RabbitMQ 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
RabbitMQCustom Resource (CR).KubeDBProvisioner operator watches theRabbitMQCR.When the operator finds a
RabbitMQCR, it creates required number ofStatefulSetsand 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
KubeDBOps-manager operator.Then, in order to expand the volume the
RabbitMQdatabase the user creates aRabbitMQOpsRequestCR with desired information.KubeDBOps-manager operator watches theRabbitMQOpsRequestCR.When it finds a
RabbitMQOpsRequestCR, it halts theRabbitMQobject which is referred from theRabbitMQOpsRequest. So, theKubeDBProvisioner operator doesn’t perform any operations on theRabbitMQobject during the volume expansion process.Then the
KubeDBOps-manager operator will expand the persistent volume to reach the expected size defined in theRabbitMQOpsRequestCR.After the successful Volume Expansion of the related StatefulSet Pods, the
KubeDBOps-manager operator updates the new volume size in theRabbitMQobject to reflect the updated state.After the successful Volume Expansion of the
RabbitMQcomponents, theKubeDBOps-manager operator resumes theRabbitMQobject so that theKubeDBProvisioner operator resumes its usual operations.
In the next docs, we are going to show a step-by-step guide on Volume Expansion of various RabbitMQ database components using RabbitMQOpsRequest CRD.































