New to KubeDB? Please start here.

Reconfiguring Redis

This guide will give an overview on how KubeDB Ops-manager operator reconfigures Redis/Valkey database.

Before You Begin

• You should be familiar with the following KubeDB concepts:
  • Redis
  • RedisOpsRequest

How Reconfiguring Redis Process Works

The following diagram shows how KubeDB Ops-manager operator reconfigures Redis database components. Open the image in a new tab to see the enlarged version.

  

The Reconfiguring Redis process consists of the following steps:

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

2. KubeDB operator watches the Redis CR.

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

4. Then, in order to reconfigure the Redis database the user creates a RedisOpsRequest CR with desired information.

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

6. When it finds a RedisOpsRequest CR, it halts the Redis object which is referred from the RedisOpsRequest. So, the KubeDB Provisioner operator doesn’t perform any operations on the Redis 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 RedisOpsRequest 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 RedisOpsRequest CR.

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