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 Vertical Autoscaling
This guide will give an overview on how KubeDB Autoscaler operator autoscales the database storage using kafkaautoscaler
crd.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Storage Autoscaling Works
The following diagram shows how KubeDB Autoscaler operator autoscales the resources of Kafka
cluster 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 (CR).KubeDB
Provisioner operator watches theKafka
CR.When the operator finds a
Kafka
CR, it creates required number ofPetSets
and related necessary stuff like secrets, services, etc.
- Each PetSet creates a Persistent Volume according to the Volume Claim Template provided in the petset configuration.
Then, in order to set up storage 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 continuously watches persistent volumes of the clusters to check if it exceeds the specified usage threshold.
- If the usage exceeds the specified usage threshold, then
KubeDB
Autoscaler operator creates aKafkaOpsRequest
to expand the storage of the database.
KubeDB
Ops-manager operator watches theKafkaOpsRequest
CRO.Then the
KubeDB
Ops-manager operator will expand the storage of the cluster component as specified on theKafkaOpsRequest
CRO.
In the next docs, we are going to show a step by step guide on Autoscaling storage of various Kafka cluster components using KafkaAutoscaler
CRD.