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:
  • Ignite
  • IgniteOpsRequest

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:

1. At first, a user creates a Ignite Custom Resource (CR).

2. KubeDB Provisioner operator watches the Ignite CR.

3. When the operator finds a Ignite CR, it creates required number of StatefulSets and related necessary stuff like secrets, services, etc.

4. 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.

5. Then, in order to expand the volume the Ignite database the user creates a IgniteOpsRequest CR with desired information.

6. KubeDB Ops-manager operator watches the IgniteOpsRequest CR.

7. When it finds a IgniteOpsRequest CR, it halts the Ignite object which is referred from the IgniteOpsRequest. So, the KubeDB Provisioner operator doesn’t perform any operations on the Ignite object during the volume expansion process.

8. Then the KubeDB Ops-manager operator will expand the persistent volume to reach the expected size defined in the IgniteOpsRequest CR.

9. After the successful Volume Expansion of the related StatefulSet Pods, the KubeDB Ops-manager operator updates the new volume size in the Ignite object to reflect the updated state.

10. After the successful Volume Expansion of the Ignite components, the KubeDB Ops-manager operator resumes the Ignite object so that the KubeDB 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.