Deploy Kafka Cluster in Azure Kubernetes Service (AKS)


KubeDB is the Kubernetes Native Database Management Solution which simplifies and automates routine database tasks such as Provisioning, Monitoring, Upgrading, Patching, Scaling, Volume Expansion, Backup, Recovery, Failure detection, and Repair for various popular databases on private and public clouds. The databases supported by KubeDB include MongoDB, Elasticsearch, MySQL, MariaDB, Redis, PostgreSQL, Percona XtraDB, and Memcached. Additionally, KubeDB also supports ProxySQL, PgBouncer, and the streaming platform Kafka. You can find the guides to all the supported databases in KubeDB . In this tutorial we will deploy Kafka Cluster in Azure Kubernetes Service (AKS). We will cover the following steps:

  1. Install KubeDB
  2. Deploy Kafka Cluster
  3. Publish & Consume Messages with Kafka

Get Cluster ID

We need the cluster ID to get the KubeDB License. To get cluster ID, we can run the following command:

$ kubectl get ns kube-system -o jsonpath='{.metadata.uid}'

Get License

Go to Appscode License Server to get the license.txt file. For this tutorial we will use KubeDB.

License Server

Install KubeDB

We will use helm to install KubeDB. Please install helm here if it is not already installed. Now, let’s install KubeDB.

$ helm search repo appscode/kubedb
appscode/kubedb                   	v2024.2.14   	v2024.2.14 	KubeDB by AppsCode - Production ready databases...
appscode/kubedb-autoscaler        	v0.27.0      	v0.27.0    	KubeDB Autoscaler by AppsCode - Autoscale KubeD...
appscode/kubedb-catalog           	v2024.2.14   	v2024.2.14 	KubeDB Catalog by AppsCode - Catalog for databa...
appscode/kubedb-community         	v0.24.2      	v0.24.2    	KubeDB Community by AppsCode - Community featur...
appscode/kubedb-crd-manager       	v0.0.5       	v0.0.5     	KubeDB CRD Manager by AppsCode
appscode/kubedb-crds              	v2024.2.14   	v2024.2.14 	KubeDB Custom Resource Definitions
appscode/kubedb-dashboard         	v0.18.0      	v0.18.0    	KubeDB Dashboard by AppsCode
appscode/kubedb-enterprise        	v0.11.2      	v0.11.2    	KubeDB Enterprise by AppsCode - Enterprise feat...
appscode/kubedb-grafana-dashboards	v2024.2.14   	v2024.2.14 	A Helm chart for kubedb-grafana-dashboards by A...
appscode/kubedb-kubestash-catalog 	v2024.2.14   	v2024.2.14 	KubeStash Catalog by AppsCode - Catalog of Kube...
appscode/kubedb-metrics           	v2024.2.14   	v2024.2.14 	KubeDB State Metrics
appscode/kubedb-one               	v2023.12.28  	v2023.12.28	KubeDB and Stash by AppsCode - Production ready...
appscode/kubedb-ops-manager       	v0.29.0      	v0.29.0    	KubeDB Ops Manager by AppsCode - Enterprise fea...
appscode/kubedb-opscenter         	v2024.2.14   	v2024.2.14 	KubeDB Opscenter by AppsCode
appscode/kubedb-provider-aws      	v2024.2.14   	v0.4.0     	A Helm chart for KubeDB AWS Provider for Crossp...
appscode/kubedb-provider-azure    	v2024.2.14   	v0.4.0     	A Helm chart for KubeDB Azure Provider for Cros...
appscode/kubedb-provider-gcp      	v2024.2.14   	v0.4.0     	A Helm chart for KubeDB GCP Provider for Crossp...
appscode/kubedb-provisioner       	v0.42.0      	v0.42.0    	KubeDB Provisioner by AppsCode - Community feat...
appscode/kubedb-schema-manager    	v0.18.0      	v0.18.0    	KubeDB Schema Manager by AppsCode
appscode/kubedb-ui                	v2024.2.13   	0.6.4      	A Helm chart for Kubernetes
appscode/kubedb-ui-server         	v2021.12.21  	v2021.12.21	A Helm chart for kubedb-ui-server by AppsCode
appscode/kubedb-webhook-server    	v0.18.0      	v0.18.0    	KubeDB Webhook Server by AppsCode

$ helm install kubedb oci:// \
  --version v2024.2.14 \
  --namespace kubedb --create-namespace \
  --set-file global.license=/path/to/the/license.txt \
  --wait --burst-limit=10000 --debug

Let’s verify the installation:

$ kubectl get pods --all-namespaces -l ""
NAMESPACE   NAME                                            READY   STATUS    RESTARTS   AGE
kubedb      kubedb-kubedb-autoscaler-58f9b5bf69-9mnlw       1/1     Running   0          2m42s
kubedb      kubedb-kubedb-ops-manager-7cfcd44796-mcndf      1/1     Running   0          2m42s
kubedb      kubedb-kubedb-provisioner-6b566ccffc-m726p      1/1     Running   0          2m42s
kubedb      kubedb-kubedb-webhook-server-6497885f5d-k5q7j   1/1     Running   0          2m42s
kubedb      kubedb-sidekick-5dc87959b7-t4lb4                1/1     Running   0          2m42s

We can list the CRD Groups that have been registered by the operator by running the following command:

$ kubectl get crd -l
NAME                                               CREATED AT                   2024-02-23T10:36:07Z                        2024-02-23T10:36:07Z                   2024-02-23T10:35:37Z    2024-02-23T10:36:04Z   2024-02-23T10:36:04Z                         2024-02-23T10:36:04Z            2024-02-23T10:36:04Z           2024-02-23T10:35:37Z                    2024-02-23T10:35:37Z                2024-02-23T10:35:37Z          2024-02-23T10:35:37Z                    2024-02-23T10:36:07Z                                  2024-02-23T10:36:07Z                   2024-02-23T10:35:37Z          2024-02-23T10:36:10Z                 2024-02-23T10:36:10Z                  2024-02-23T10:36:10Z                                2024-02-23T10:36:10Z                 2024-02-23T10:35:37Z               2024-02-23T10:35:37Z               2024-02-23T10:36:14Z          2024-02-23T10:36:14Z                 2024-02-23T10:36:14Z                  2024-02-23T10:36:14Z                                2024-02-23T10:36:14Z                 2024-02-23T10:35:37Z                 2024-02-23T10:36:17Z            2024-02-23T10:36:17Z                   2024-02-23T10:36:17Z                    2024-02-23T10:36:17Z                                  2024-02-23T10:36:17Z                   2024-02-23T10:35:37Z           2024-02-23T10:35:37Z               2024-02-23T10:35:37Z                  2024-02-23T10:35:37Z              2024-02-23T10:36:21Z         2024-02-23T10:36:21Z                2024-02-23T10:36:21Z                              2024-02-23T10:36:20Z                 2024-02-23T10:36:21Z                2024-02-23T10:35:37Z                2024-02-23T10:35:37Z                     2024-02-23T10:36:21Z                2024-02-23T10:35:37Z            2024-02-23T10:36:24Z                                 2024-02-23T10:36:24Z                    2024-02-23T10:36:24Z    2024-02-23T10:36:24Z            2024-02-23T10:36:24Z                          2024-02-23T10:36:24Z                   2024-02-23T10:35:37Z             2024-02-23T10:35:37Z                    2024-02-23T10:35:37Z                    2024-02-23T10:36:21Z               2024-02-23T10:35:37Z

Deploy Kafka Cluster

We are going to Deploy Kafka Cluster by using KubeDB. First, let’s create a Namespace in which we will deploy Kafka.

$ kubectl create namespace demo
namespace/demo created

Here is the yaml of the Kafka CR we are going to use:

kind: Kafka
  name: kafka-cluster
  namespace: demo
  replicas: 3
  version: 3.6.0
      - ReadWriteOnce
        storage: 1Gi
    storageClassName: default
  storageType: Durable
  terminationPolicy: WipeOut

Let’s save this yaml configuration into kafka-cluster.yaml Then create the above Kafka CR

$ kubectl apply -f kafka-cluster.yaml created

In this yaml,

  • spec.version field specifies the version of Kafka. Here, we are using Kafka 3.6.0. You can list the KubeDB supported versions of Kafka by running $ kubectl get kafkaversions command.
  • is the name of the StorageClass used to provision PVCs.
  • spec.terminationPolicy field is Wipeout means it will be deleted without restrictions. It can also be “Halt”, “Delete” and “DoNotTerminate”. Learn More about these checkout Termination Policy .

Once these are handled correctly and the Kafka object is deployed, you will see that the following objects are created:

$ kubectl get all,secret -n demo -l ''
NAME                  READY   STATUS    RESTARTS   AGE
pod/kafka-cluster-0   1/1     Running   0          3m10s
pod/kafka-cluster-1   1/1     Running   0          2m8s
pod/kafka-cluster-2   1/1     Running   0          2m2s

NAME                         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                       AGE
service/kafka-cluster-pods   ClusterIP   None         <none>        9092/TCP,9093/TCP,29092/TCP   3m11s

NAME                             READY   AGE
statefulset.apps/kafka-cluster   3/3     3m10s

NAME                                               TYPE               VERSION   AGE   3.6.0     3m10s

NAME                              TYPE                       DATA   AGE
secret/kafka-cluster-admin-cred   2      3m11s
secret/kafka-cluster-config       Opaque                     2      3m11s

Let’s check if the kafka-cluster is ready to use,

$ kubectl get kafka -n demo kafka-cluster
NAME            TYPE                  VERSION   STATUS   AGE
kafka-cluster   3.6.0     Ready    3m30s

We have successfully deployed Kafka cluster in AKS.

Publish & Consume Messages with Kafka

Accessing Kafka Through CLI

In this section, we will now exec into one of the kafka brokers in interactive mode and then describe the broker metadata for the quorum.

$ kubectl exec -it -n demo  kafka-cluster-0 -- bash
kafka@kafka-cluster-0:~$ --command-config $HOME/config/ --bootstrap-server localhost:9092 describe --status
ClusterId:              11ee-bc31-d66cd1c62f3w
LeaderId:               1
LeaderEpoch:            14
HighWatermark:          392
MaxFollowerLag:         0
MaxFollowerLagTimeMs:   350
CurrentVoters:          [0,1,2]
CurrentObservers:       []

We can see the important metadata information like clusterID, current leader ID, node IDs which are participating in leader election voting and IDs of those brokers who are observers. It is important to mention that each broker is assigned a numeric ID which is called its broker ID. The ID is assigned sequentially with respect to the host pod name.

Create a Topic

Let’s create a topic named music with 3 partitions and a replication factor of 3. Describe the topic once it’s created. You will see the leader ID for each partition and their replica IDs along with in-sync-replicas(ISR).

$ kubectl exec -it -n demo  kafka-cluster-0 -- bash

kafka@kafka-cluster-0:~$ --create  --bootstrap-server localhost:9092 --command-config $HOME/config/ --topic music --partitions 3 --replication-factor 3

Created topic music.

kafka@kafka-cluster-0:~$ --describe --topic music --bootstrap-server localhost:9092 --command-config $HOME/config/

Topic: music	TopicId: 2iCBGBHyQDa2iImRBJmJ6g	PartitionCount: 3	ReplicationFactor: 3	Configs: segment.bytes=1073741824,
	Topic: music	Partition: 0	Leader: 1	Replicas: 1,2,0	Isr: 1,2,0
	Topic: music	Partition: 1	Leader: 2	Replicas: 2,0,1	Isr: 2,0,1
	Topic: music	Partition: 2	Leader: 0	Replicas: 0,1,2	Isr: 0,1,2

Now, we are going to start a producer and a consumer for topic music. Let’s use this current terminal for producing messages and open a new terminal for consuming messages. From the topic description we can see that the leader partition for partition 0 is 1 (the broker that we are on). If we produce messages to kafka-cluster-1 broker(brokerID=1) it will store those messages in partition 0 and --request-required-acks all ensures that the message is durably stored on all replicas before the producer considers the message sent. Let’s produce messages in the producer terminal and consume them from the consumer terminal.

$ kubectl exec -it -n demo  kafka-cluster-1 -- bash
kafka@kafka-cluster-1:~$  --topic music --request-required-acks all --bootstrap-server localhost:9092 --producer.config $HOME/config/

>Five Hundred Miles
>It's My Life
>Country Roads Take Me Home
$ kubectl exec -it -n demo  kafka-cluster-1 -- bash
kafka@kafka-cluster-1:~$ --topic music --from-beginning --bootstrap-server localhost:9092 --consumer.config $HOME/config/

Five Hundred Miles
It's My Life
Country Roads Take Me Home

Here we can see messages are coming to the consumer as you continue sending messages via producer. So, we have created a Kafka topic and used Kafka console producer and consumer for publishing and consuming messages successfully. More information about Run & Manage Kafka on Kubernetes can be found in Kafka Kubernetes

If you want to learn about Kafka Ops Requests - Day 2 Lifecycle Management Using KubeDB you can have a look into that video below:


To speak with us, please leave a message on our website .

To receive product announcements, follow us on Twitter/X .

To watch tutorials of various Production-Grade Kubernetes Tools Subscribe to our YouTube channel.

Learn more about Kafka in Kubernetes

If you have found a bug with KubeDB or want to request for new features, please file an issue .


Get Up and Running Quickly

Deploy, manage, upgrade Kubernetes on any cloud and automate deployment, scaling, and management of containerized applications.