New to KubeDB? Please start here.

Ignite Horizontal Scaling

This guide will give an overview on how KubeDB Ops-manager operator scales up or down Ignite cluster.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • Ignite
  • IgniteOpsRequest

How Horizontal Scaling Process Works

The following diagram shows how KubeDB Ops-manager operator scales up or down Ignite database components. Open the image in a new tab to see the enlarged version.

The Horizontal scaling 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 PetSets and related necessary stuff like secrets, services, etc.

4. Then, in order to scale the Ignite cluster, the user creates a IgniteOpsRequest CR with desired information.

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

6. 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 horizontal scaling process.

7. Then the KubeDB Ops-manager operator will scale the related PetSet Pods to reach the expected number of replicas defined in the IgniteOpsRequest CR.

8. After the successfully scaling the replicas of the related PetSet Pods, the KubeDB Ops-manager operator updates the number of replicas in the Ignite object to reflect the updated state.

9. After the successful scaling of the Ignite replicas, 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 horizontal scaling of Ignite database using IgniteOpsRequest CRD.