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 Volume Expansion

This guide will give an overview on how KubeDB Ops-manager operator expand the volume of various component of Kafka like:. (Combined and Topology).

Before You Begin

How Volume Expansion Process Works

The following diagram shows how KubeDB Ops-manager operator expand the volumes of Kafka database components. Open the image in a new tab to see the enlarged version.

  Volume Expansion process of Kafka
Fig: Volume Expansion process of Kafka

The Volume Expansion process consists of the following steps:

  1. At first, a user creates a Kafka Custom Resource (CR).

  2. KubeDB Provisioner operator watches the Kafka CR.

  3. When the operator finds a Kafka CR, it creates required number of PetSets and related necessary stuff like secrets, services, etc.

  4. Each PetSet creates a Persistent Volume according to the Volume Claim Template provided in the petset configuration. This Persistent Volume will be expanded by the KubeDB Ops-manager operator.

  5. Then, in order to expand the volume of the various components (ie. Combined, Broker, Controller) of the Kafka, the user creates a KafkaOpsRequest CR with desired information.

  6. KubeDB Ops-manager operator watches the KafkaOpsRequest CR.

  7. When it finds a KafkaOpsRequest CR, it halts the Kafka object which is referred from the KafkaOpsRequest. So, the KubeDB Provisioner operator doesn’t perform any operations on the Kafka object during the volume expansion process.

  8. Then the KubeDB Ops-manager operator will expand the persistent volume to reach the expected size defined in the KafkaOpsRequest CR.

  9. After the successful Volume Expansion of the related PetSet Pods, the KubeDB Ops-manager operator updates the new volume size in the Kafka object to reflect the updated state.

  10. After the successful Volume Expansion of the Kafka components, the KubeDB Ops-manager operator resumes the Kafka object so that the KubeDB Provisioner operator resumes its usual operations.

In the next docs, we are going to show a step-by-step guide on Volume Expansion of various Kafka database components using KafkaOpsRequest CRD.