This is an Enterprise-only feature. Please install KubeDB Enterprise Edition to try this feature.
New to KubeDB? Please start here.
This guide will give you an overview on how KubeDB Enterprise operator updates the resources(for example CPU and Memory etc.) of the
The following diagram shows how KubeDB Enterprise operator updates the resources of the
Redis database. Open the image in a new tab to see the enlarged version.
The vertical scaling process consists of the following steps:
At first, a user creates a
Redis Custom Resource (CR).
KubeDB Community operator watches the
When the operator finds a
Redis CR, it creates required number of
StatefulSets and related necessary stuff like appbinding, services, etc.
Then, in order to update the resources(for example
Memory etc.) of the
Redis database the user creates a
RedisOpsRequest CR with desired information.
KubeDB Enterprise operator watches the
When it finds a
RedisOpsRequest CR, it halts the
Redis object which is referred from the
RedisOpsRequest. So, the
KubeDB Community operator doesn’t perform any operations on the
Redis object during the vertical scaling process.
KubeDB Enterprise operator will update resources of the StatefulSet Pods to reach desired state.
After the successful update of the resources of the StatefulSet’s replica, the
KubeDB Enterprise operator updates the
Redis object to reflect the updated state.
After the successful update of the
Redis resources, the
KubeDB Enterprise operator resumes the
Redis object so that the
KubeDB Community operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on updating resources of Redis database using