You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
We use cookies and other similar technology to collect data to improve your experience on our site, as described in our Privacy Policy.
Run Production-Grade Databases on Kubernetes
Backup and Recovery Solution for Kubernetes
Run Production-Grade Vault on Kubernetes
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
KubeDB simplifies Provision, Upgrade, Scaling, Volume Expansion, Monitor, Backup, Restore for various Databases in Kubernetes on any Public & Private Cloud
A complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.
KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp's Vault on Kubernetes.
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
New to KubeDB? Please start here.
This guide will give an overview on how KubeDB Autoscaler operator autoscales the database compute resources i.e. cpu and memory using redisautoscaler crd.
KubeDB concepts:
The following diagram shows how KubeDB Autoscaler operator autoscales the resources of Redis 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 Redis/RedisSentinel Custom Resource Object (CRO).
KubeDB Provisioner operator watches the Redis/RedisSentinel CRO.
When the operator finds a Redis/RedisSentinel CRO, it creates required number of StatefulSets and related necessary stuff like secrets, services, etc.
Then, in order to set up autoscaling of the Redis database the user creates a RedisAutoscaler CRO with desired configuration.
Then, in order to set up autoscaling of the RedisSentinel database the user creates a RedisSentinelAutoscaler CRO with desired configuration.
KubeDB Autoscaler operator watches the RedisAutoscaler && RedisSentinelAutoscaler CRO.
KubeDB Autoscaler operator generates recommendation using the modified version of kubernetes official recommender for the database, as specified in the RedisAutoscaler/RedisSentinelAutoscaler CRO.
If the generated recommendation doesn’t match the current resources of the database, then KubeDB Autoscaler operator creates a RedisOpsRequest/RedisSentinelOpsRequest CRO to scale the database to match the recommendation generated.
KubeDB Ops-manager operator watches the RedisOpsRequest/RedisSentinelOpsRequest CRO.
Then the KubeDB ops-manager operator will scale the database component vertically as specified on the RedisOpsRequest/RedisSentinelOpsRequest CRO.
In the next docs, we are going to show a step-by-step guide on Autoscaling of various Redis database components using RedisAutoscaler/RedisSentinelAutoscaler CRD.