Helm charts for Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Kafka chart repository URL.

Kafka

helm repo add kafka [1]

Drag options to blanks, or click blank then click option'

Ahttps://charts.helm.sh/stable

Bhttps://kafka.apache.org/charts

Chttps://charts.bitnami.com/bitnami

Dhttps://charts.example.com/kafka

Attempts:

3 left

💡 Hint

Common Mistakes

Using the Apache Kafka website URL instead of the Helm chart repo URL.

Using an outdated or incorrect chart repository URL.

The Bitnami Helm chart repository URL is https://charts.bitnami.com/bitnami, which hosts the Kafka charts.

2fill in blank

medium

Complete the command to install Kafka using Helm with the release name 'my-kafka'.

Kafka

helm install my-kafka kafka/[1]

Drag options to blanks, or click blank then click option'

Abroker

Bzookeeper

Ckafkacluster

Dkafka

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'zookeeper' which is a separate chart.

Using incorrect chart names like 'broker' or 'kafkacluster'.

The chart name to install Kafka from the Bitnami repo is kafka.

3fill in blank

hard

Fix the error in the values override to set the Kafka broker count to 3.

Kafka

replicaCount: [1]

Drag options to blanks, or click blank then click option'

A3

Bthree

C1

D'3'

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string like '3' instead of a number.

Using words like 'three' which is invalid.

The replicaCount value must be an integer without quotes. Setting it to 3 creates 3 Kafka brokers.

4fill in blank

hard

Fill both blanks to configure Kafka to use persistent storage with 10Gi size.

Kafka

persistence:
  enabled: [1]
  size: [2]

Drag options to blanks, or click blank then click option'

Atrue

Bfalse

C10Gi

D5Gi

Attempts:

3 left

💡 Hint

Common Mistakes

Disabling persistence by setting enabled to false.

Using incorrect size values like '5Gi'.

To enable persistent storage, set enabled to true and specify the size as 10Gi.

5fill in blank

hard

Fill all three blanks to set Kafka's advertised listeners for external access.

Kafka

externalAccess:
  enabled: [1]
  service:
    type: [2]
  autoDiscovery:
    enabled: [3]

Drag options to blanks, or click blank then click option'

Afalse

BLoadBalancer

Ctrue

DNodePort

Attempts:

3 left

💡 Hint

Common Mistakes

Disabling external access by setting enabled to false.

Using NodePort instead of LoadBalancer when LoadBalancer is required.

To enable external access, set enabled and autoDiscovery.enabled to true, and use LoadBalancer service type.

Practice

1. What is the main purpose of using Helm charts for Kafka deployment on Kubernetes?

easy

A. To automate and simplify Kafka deployment and management

B. To write Kafka application code

C. To monitor Kafka topics manually

D. To replace Kafka brokers with databases

Solution

1. Step 1: Understand Helm charts role

   Helm charts package Kubernetes resources to automate deployment and management.

2. Step 2: Apply to Kafka context

   Using Helm charts for Kafka automates its deployment and configuration on Kubernetes clusters.

3. Final Answer:

   To automate and simplify Kafka deployment and management -> Option A

4. Quick Check:

   Helm automates Kafka deployment = B [OK]

Hint: Helm automates deployment tasks for Kafka on Kubernetes [OK]

Common Mistakes:

• Confusing Helm with Kafka application coding
• Thinking Helm replaces Kafka brokers
• Assuming Helm is for manual monitoring

2. Which Helm command syntax correctly sets the Kafka broker count to 3 during installation?

easy

A. helm install kafka bitnami/kafka --set brokerCount=3

B. helm install kafka bitnami/kafka --set brokers=3

C. helm install kafka bitnami/kafka --set replicaCount=3

D. helm install kafka bitnami/kafka --set kafka.broker=3

Solution

1. Step 1: Identify correct Helm parameter for replicas

   Common Helm charts use replicaCount to set number of pods/brokers.

2. Step 2: Match parameter with Kafka Helm chart

   Bitnami Kafka chart uses replicaCount to define broker count.

3. Final Answer:

   helm install kafka bitnami/kafka --set replicaCount=3 -> Option C

4. Quick Check:

   replicaCount sets broker pods = A [OK]

Hint: Use replicaCount to set broker number in Helm [OK]

Common Mistakes:

• Using incorrect parameter names like brokers or brokerCount
• Misplacing dot notation in --set
• Confusing Helm install syntax

3. Given this Helm command:

helm install kafka bitnami/kafka --set replicaCount=2,logRetentionHours=168

What will be the effect on the Kafka deployment?

medium

A. Deploy 2 Kafka brokers with logs retained for 168 hours

B. Deploy 168 Kafka brokers with 2 hours log retention

C. Deploy 2 Kafka brokers with default log retention

D. Deployment will fail due to syntax error

Solution

1. Step 1: Analyze replicaCount setting

   replicaCount=2 means 2 Kafka broker pods will be deployed.

2. Step 2: Analyze logRetentionHours setting

   logRetentionHours=168 sets log retention to 168 hours (7 days).

3. Final Answer:

   Deploy 2 Kafka brokers with logs retained for 168 hours -> Option A

4. Quick Check:

   replicaCount=2 and logRetentionHours=168 = D [OK]

Hint: Check each --set key=value carefully for effect [OK]

Common Mistakes:

• Mixing up values of replicaCount and logRetentionHours
• Assuming syntax error due to comma
• Ignoring log retention setting

4. You run this Helm upgrade command:

helm upgrade kafka bitnami/kafka --set replicaCount=3

But the Kafka deployment still has 2 brokers. What is the likely issue?

medium

A. The Helm chart version is incompatible

B. The Helm release name is incorrect

C. Kafka does not support scaling brokers via Helm

D. The replicaCount value was not applied due to missing --reuse-values flag

Solution

1. Step 1: Understand Helm upgrade behavior

   Helm upgrade requires --reuse-values to reuse previous values while applying new --set overrides.

2. Step 2: Identify why replicaCount didn't change

   Without --reuse-values, the new value may not apply correctly in combination with prior settings.

3. Final Answer:

   The replicaCount value was not applied due to missing --reuse-values flag -> Option D

4. Quick Check:

   Missing --reuse-values can block value changes = A [OK]

Hint: Use --reuse-values to keep and update Helm settings on upgrade [OK]

Common Mistakes:

• Assuming Helm release name is wrong
• Believing Kafka can't scale brokers
• Ignoring Helm chart version compatibility

5. You want to deploy Kafka with 3 brokers and customize the storage size to 50Gi using Helm. Which command correctly achieves this?

hard

A. helm install kafka bitnami/kafka --set replicaCount=3,storage.size=50Gi

B. helm install kafka bitnami/kafka --set replicaCount=3 --set persistence.size=50Gi

C. helm install kafka bitnami/kafka --set brokers=3 --set storage.size=50Gi

D. helm install kafka bitnami/kafka --set replicaCount=3 --set persistence.storage=50Gi

Solution

1. Step 1: Set broker count correctly

   replicaCount=3 sets 3 Kafka brokers.

2. Step 2: Set storage size correctly

   Bitnami Kafka chart uses persistence.size to define storage size per broker.

3. Step 3: Use correct Helm syntax

   Separate --set flags or comma-separated values are valid, but helm install kafka bitnami/kafka --set replicaCount=3 --set persistence.size=50Gi uses clear separate flags.

4. Final Answer:

   helm install kafka bitnami/kafka --set replicaCount=3 --set persistence.size=50Gi -> Option B

5. Quick Check:

   replicaCount and persistence.size set correctly = C [OK]

Hint: Use replicaCount and persistence.size keys for brokers and storage [OK]

Common Mistakes:

• Using wrong keys like brokers or storage.size
• Combining keys incorrectly in one --set
• Using persistence.storage instead of persistence.size