New to KubeDB? Please start here.

Qdrant Volume Expansion

This guide will give an overview of how KubeDB Ops-manager expands the volume of a Qdrant database.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • Qdrant
  • QdrantOpsRequest

How Volume Expansion Process Works

The following diagram shows how KubeDB Ops Manager expand the volumes of Qdrant 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 Qdrant Custom Resource (CR).

2. KubeDB-Provisioner operator watches the Qdrant CR.

3. When the operator finds a Qdrant CR, it creates a Petset and related necessary stuff like pods, PVCs, secrets, services, etc.

4. Each Petset creates a Persistent Volume according to the volume claim template. This Persistent Volume will be expanded by the KubeDB Ops-manager operator.

5. Then, in order to expand the volume of the Qdrant database, the user creates a QdrantOpsRequest CR with the desired new storage size.

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

7. When it finds a QdrantOpsRequest CR, it pauses the Qdrant object so that the KubeDB-Provisioner operator doesn’t perform any operations on the Qdrant during the volume expansion process.

8. Then the KubeDB Ops-manager operator expands the persistent volumes to the expected size defined in the QdrantOpsRequest CR.

9. After the successful expansion of the volumes, the KubeDB Ops-manager updates the new volume size in the Qdrant object to reflect the updated state.

10. After the successful Volume Expansion, the KubeDB Ops-manager resumes the Qdrant object so that the KubeDB-Provisioner resumes its usual operations.

In the next doc, we are going to show a step-by-step guide on Volume Expansion of a Qdrant database using QdrantOpsRequest CRD.