You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
New to KubeDB? Please start here.
Kafka Compute Resource Autoscaling
This guide will give an overview on how KubeDB Autoscaler operator autoscales the database compute resources i.e. cpu and memory using kafkaautoscaler
crd.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Compute Autoscaling Works
The following diagram shows how KubeDB Autoscaler operator autoscales the resources of Kafka
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
Kafka
Custom Resource Object (CRO).KubeDB
Provisioner operator watches theKafka
CRO.When the operator finds a
Kafka
CRO, it creates required number ofPetSets
and related necessary stuff like secrets, services, etc.Then, in order to set up autoscaling of the various components (ie. Combined, Broker, Controller) of the
Kafka
cluster the user creates aKafkaAutoscaler
CRO with desired configuration.KubeDB
Autoscaler operator watches theKafkaAutoscaler
CRO.KubeDB
Autoscaler operator generates recommendation using the modified version of kubernetes official recommender for different components of the database, as specified in theKafkaAutoscaler
CRO.If the generated recommendation doesn’t match the current resources of the database, then
KubeDB
Autoscaler operator creates aKafkaOpsRequest
CRO to scale the database to match the recommendation generated.KubeDB
Ops-manager operator watches theKafkaOpsRequest
CRO.Then the
KubeDB
Ops-manager operator will scale the database component vertically as specified on theKafkaOpsRequest
CRO.
In the next docs, we are going to show a step by step guide on Autoscaling of various Kafka database components using KafkaAutoscaler
CRD.