New to KubeDB? Please start here.

Reconfiguring SingleStore

This guide will give an overview on how KubeDB Ops Manager reconfigures SingleStore.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • SingleStore
  • SingleStoreOpsRequest

How Reconfiguring SingleStore Process Works

The following diagram shows how KubeDB Ops Manager reconfigures SingleStore database components. Open the image in a new tab to see the enlarged version.

  

The Reconfiguring SingleStore process consists of the following steps:

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

2. KubeDB Provisioner operator watches the SingleStore CR.

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

4. Then, in order to reconfigure the SingleStore standalone or cluster the user creates a SingleStoreOpsRequest CR with desired information.

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

6. When it finds a SingleStoreOpsRequest CR, it halts the SingleStore object which is referred from the SingleStoreOpsRequest. So, the KubeDB provisioner operator doesn’t perform any operations on the SingleStore object during the reconfiguring process.

7. 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 the SingleStoreOpsRequest CR.

8. Then the KubeDB Ops-manager operator will restart the related PetSet Pods so that they restart with the new configuration defined in the SingleStoreOpsRequest CR.

9. After the successful reconfiguring of the SingleStore, the KubeDB Ops-manager operator resumes the SingleStore 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 reconfiguring SingleStore database components using SingleStoreOpsRequest CRD.