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
KubeDBconcepts:
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
KafkaCustom Resource Object (CRO).KubeDBProvisioner operator watches theKafkaCRO.When the operator finds a
KafkaCRO, it creates required number ofPetSetsand related necessary stuff like secrets, services, etc.Then, in order to set up autoscaling of the various components (ie. Combined, Broker, Controller) of the
Kafkacluster the user creates aKafkaAutoscalerCRO with desired configuration.KubeDBAutoscaler operator watches theKafkaAutoscalerCRO.KubeDBAutoscaler operator generates recommendation using the modified version of kubernetes official recommender for different components of the database, as specified in theKafkaAutoscalerCRO.If the generated recommendation doesn’t match the current resources of the database, then
KubeDBAutoscaler operator creates aKafkaOpsRequestCRO to scale the database to match the recommendation generated.KubeDBOps-manager operator watches theKafkaOpsRequestCRO.Then the
KubeDBOps-manager operator will scale the database component vertically as specified on theKafkaOpsRequestCRO.
In the next docs, we are going to show a step by step guide on Autoscaling of various Kafka database components using KafkaAutoscaler CRD.






























