New to KubeDB? Please start here.
Kafka Update Version Overview
This guide will give you an overview on how KubeDB Ops-manager operator update the version of Kafka
.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How update version Process Works
The following diagram shows how KubeDB Ops-manager operator used to update the version of Kafka
. Open the image in a new tab to see the enlarged version.
The updating 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.Then, in order to update the version of the
Kafka
database the user creates aKafkaOpsRequest
CR with the desired version.KubeDB
Ops-manager operator watches theKafkaOpsRequest
CR.When it finds a
KafkaOpsRequest
CR, it halts theKafka
object which is referred from theKafkaOpsRequest
. So, theKubeDB
Provisioner operator doesn’t perform any operations on theKafka
object during the updating process.By looking at the target version from
KafkaOpsRequest
CR,KubeDB
Ops-manager operator updates the images of all thePetSets
.After successfully updating the
PetSets
and theirPods
images, theKubeDB
Ops-manager operator updates the image of theKafka
object to reflect the updated state of the database.After successfully updating of
Kafka
object, theKubeDB
Ops-manager operator resumes theKafka
object so that theKubeDB
Provisioner operator can resume its usual operations.
In the next doc, we are going to show a step by step guide on updating of a Kafka database using updateVersion operation.