Helm charts for Kafka - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of Helm install command with default Kafka chart values?

You run the command helm install my-kafka bitnami/kafka with default values. What will be the status of the Kafka pods immediately after installation?

A Kafka pods will be in <strong>Pending</strong> state indefinitely due to missing PVCs.

B Kafka pods will be in <strong>Running</strong> state after a few seconds.

C Kafka pods will fail to start with <strong>CrashLoopBackOff</strong> error.

D Kafka pods will be <strong>Completed</strong> and exit immediately.

💡 Hint

Default Bitnami Kafka Helm chart provisions persistent storage and readiness probes.

The default Bitnami Kafka Helm chart provisions persistent volumes and readiness probes, so pods start and reach Running state after initialization.

🧠 Conceptual

intermediate

Which Helm value controls the number of Kafka broker replicas?

In the Kafka Helm chart, which value key sets how many Kafka broker pods will be created?

A replicaCount

B brokers.count

C kafka.brokerReplicas

D broker.replicas

💡 Hint

Look for the common Helm pattern for replica count.

The standard Helm chart pattern uses replicaCount to specify the number of pods for the main component, including Kafka brokers.

🔧 Debug

advanced

Why does Kafka pod fail with 'CrashLoopBackOff' after Helm install?

You installed Kafka using Helm with a custom values file that disables persistence (persistence.enabled=false). The Kafka pod fails with CrashLoopBackOff. What is the most likely cause?

A The Helm chart does not support disabling persistence; it causes syntax errors.

B The Kafka image version is incompatible with Kubernetes version.

C Kafka requires persistent storage; disabling persistence causes startup failure.

D Kafka broker count is zero, so no pods are created.

💡 Hint

Think about Kafka's need for data storage and state.

Kafka brokers need persistent storage for logs and data. Disabling persistence means no storage is available, causing the broker to crash.

📝 Syntax

advanced

Identify the correct Helm values YAML snippet to enable Kafka TLS encryption

Which YAML snippet correctly enables TLS encryption for Kafka brokers in the Helm values file?

A

tls:
  enabled: true
  autoGenerate: true

B

tls:
  enabled: yes
  autoGenerated: true

C

tls:
  enable: true
  autoGenerated: true

D

tls:
  enabled: true
  autoGenerated: true

💡 Hint

Check the exact key names and boolean values.

The Bitnami Kafka Helm chart uses tls.enabled and tls.autoGenerated keys with boolean true/false values.

🚀 Application

expert

How to upgrade Kafka Helm chart to add a new broker without downtime?

You have a Kafka cluster deployed with 3 brokers using Helm. You want to upgrade the cluster to 4 brokers without downtime. Which approach is correct?

A Update <code>replicaCount</code> to 4 in values and run <code>helm upgrade</code>. Kafka will add the broker gracefully.

B Delete the Kafka release and reinstall with 4 brokers to avoid conflicts.

C Scale the StatefulSet manually to 4 replicas, then update Helm values to match.

D Change <code>replicaCount</code> to 4 and run <code>helm upgrade --force</code> to recreate pods.

💡 Hint

Think about Helm upgrade behavior and Kafka broker scaling.

Updating replicaCount and running helm upgrade will add a new broker pod gracefully without downtime. Deleting or forcing pod recreation causes downtime.