New to KubeDB? Please start here.
Ignite Vertical Autoscaling
This guide will give an overview on how KubeDB Autoscaler operator autoscales the database storage using Igniteautoscaler
crd.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Storage Autoscaling Works
The following diagram shows how KubeDB Autoscaler operator autoscales the resources of Ignite
database components. Open the image in a new tab to see the enlarged version.
The Auto Scaling 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 statefulset configuration.
Then, in order to set up storage autoscaling of the
Ignite
cluster, the user creates aIgniteAutoscaler
CRO with desired configuration.KubeDB
Autoscaler operator watches theIgniteAutoscaler
CRO.KubeDB
Autoscaler operator continuously watches persistent volumes of the databases to check if it exceeds the specified usage threshold.
- If the usage exceeds the specified usage threshold, then
KubeDB
Autoscaler operator creates aIgniteOpsRequest
to expand the storage of the database.
KubeDB
Ops-manager operator watches theIgniteOpsRequest
CRO.Then the
KubeDB
Ops-manager operator will expand the storage of the database component as specified on theIgniteOpsRequest
CRO.
In the next docs, we are going to show a step by step guide on Autoscaling storage of various Ignite database components using IgniteAutoscaler
CRD.