New to KubeDB? Please start here.
Reconfiguring Ignite
This guide will give an overview on how KubeDB Ops-manager operator reconfigures Ignite
cluster.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How does Reconfiguring Ignite Process Works
The following diagram shows how KubeDB Ops-manager operator reconfigures Ignite
database components. Open the image in a new tab to see the enlarged version.

The Reconfiguring Ignite 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 ofPetSets
and related necessary stuff like secrets, services, etc.Then, in order to reconfigure the
Ignite
database the user creates aIgniteOpsRequest
CR with desired information.KubeDB
Ops-manager operator watches theIgniteOpsRequest
CR.When it finds a
IgniteOpsRequest
CR, it halts theIgnite
object which is referred from theIgniteOpsRequest
. So, theKubeDB
Provisioner operator doesn’t perform any operations on theIgnite
object during the reconfiguring process.Then the
KubeDB
Ops-manager operator will replace the existing configuration with the new configuration provided or merge the new configuration with the existing configuration according to theMogoDBOpsRequest
CR.Then the
KubeDB
Ops-manager operator will restart the related PetSet Pods so that they restart with the new configuration defined in theIgniteOpsRequest
CR.After the successful reconfiguring of the
Ignite
components, theKubeDB
Ops-manager operator resumes theIgnite
object so that theKubeDB
Provisioner operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on reconfiguring Ignite database components using IgniteOpsRequest
CRD.