Helm install kafka

https://bitnami.com/stack/kafka/helm

helm install my-kafka oci://registry-1.docker.io/bitnamicharts/kafka

Pulled: registry-1.docker.io/bitnamicharts/kafka:27.1.2
Digest: sha256:55f64d2ec3615d8c5a6758462ccf16f3c922bb3fe298b50f3e423222e00c9d04
NAME: my-release
LAST DEPLOYED: Thu Mar 21 12:06:13 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
CHART NAME: kafka
CHART VERSION: 27.1.2
APP VERSION: 3.7.0

** Please be patient while the chart is being deployed **

Kafka can be accessed by consumers via port 9092 on the following DNS name from within your cluster:

    my-release-kafka.default.svc.cluster.local

Each Kafka broker can be accessed by producers via port 9092 on the following DNS name(s) from within your cluster:

    my-release-kafka-controller-0.my-release-kafka-controller-headless.default.svc.cluster.local:9092
    my-release-kafka-controller-1.my-release-kafka-controller-headless.default.svc.cluster.local:9092
    my-release-kafka-controller-2.my-release-kafka-controller-headless.default.svc.cluster.local:9092

The CLIENT listener for Kafka client connections from within your cluster have been configured with the following security settings:
    - SASL authentication

To connect a client to your Kafka, you need to create the 'client.properties' configuration files with the content below:

security.protocol=SASL_PLAINTEXT
sasl.mechanism=SCRAM-SHA-256
sasl.jaas.config=org.apache.kafka.common.security.scram.ScramLoginModule required \
    username="user1" \
    password="$(kubectl get secret my-release-kafka-user-passwords --namespace default -o jsonpath='{.data.client-passwords}' | base64 -d | cut -d , -f 1)";

To create a pod that you can use as a Kafka client run the following commands:

    kubectl run my-release-kafka-client --restart='Never' --image docker.io/bitnami/kafka:3.7.0-debian-12-r0 --namespace default --command -- sleep infinity
    kubectl cp --namespace default /path/to/client.properties my-release-kafka-client:/tmp/client.properties
    kubectl exec --tty -i my-release-kafka-client --namespace default -- bash

    PRODUCER:
        kafka-console-producer.sh \
            --producer.config /tmp/client.properties \
            --broker-list my-release-kafka-controller-0.my-release-kafka-controller-headless.default.svc.cluster.local:9092,my-release-kafka-controller-1.my-release-kafka-controller-headless.default.svc.cluster.local:9092,my-release-kafka-controller-2.my-release-kafka-controller-headless.default.svc.cluster.local:9092 \
            --topic test

    CONSUMER:
        kafka-console-consumer.sh \
            --consumer.config /tmp/client.properties \
            --bootstrap-server my-release-kafka.default.svc.cluster.local:9092 \
            --topic test \
            --from-beginning

WARNING: There are "resources" sections in the chart not set. Using "resourcesPreset" is not recommended for production. For production installations, please set the following values according to your workload needs:
  - controller.resources
+info https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/

kafka-controller

See also

• Kafka, kafka-cluster -h, kafka-configs, kafka-features, kafka-topics, kafka-consumer-groups, kafka-storage, kafka-server-start, kafka-server-stop, kafka-reassign-partitions, kafka-topics, kafka-console-producer, Amazon MSK, Kafka Connect, 9092, server.properties, KRaft, Kafka changelog