mirror of
https://github.com/Telecominfraproject/wlan-cloud-helm.git
synced 2025-10-29 09:42:29 +00:00
97005dcbf3
- Added charts for Kafka and zookeeper - Also updated opensync-mosquitto chart to be a Statefulset instead of deployment
68 lines
2.7 KiB
Plaintext
68 lines
2.7 KiB
Plaintext
### Connecting to Kafka from inside Kubernetes
|
|
|
|
You can connect to Kafka by running a simple pod in the K8s cluster like this with a configuration like this:
|
|
|
|
apiVersion: v1
|
|
kind: Pod
|
|
metadata:
|
|
name: testclient
|
|
namespace: {{ .Release.Namespace }}
|
|
spec:
|
|
containers:
|
|
- name: kafka
|
|
image: {{ .Values.image }}:{{ .Values.imageTag }}
|
|
command:
|
|
- sh
|
|
- -c
|
|
- "exec tail -f /dev/null"
|
|
|
|
Once you have the testclient pod above running, you can list all kafka
|
|
topics with:
|
|
|
|
kubectl -n {{ .Release.Namespace }} exec testclient -- kafka-topics --zookeeper {{ .Release.Name }}-zookeeper:2181 --list
|
|
|
|
To create a new topic:
|
|
|
|
kubectl -n {{ .Release.Namespace }} exec testclient -- kafka-topics --zookeeper {{ .Release.Name }}-zookeeper:2181 --topic test1 --create --partitions 1 --replication-factor 1
|
|
|
|
To listen for messages on a topic:
|
|
|
|
kubectl -n {{ .Release.Namespace }} exec -ti testclient -- kafka-console-consumer --bootstrap-server {{ include "common.fullname" . }}:9092 --topic test1 --from-beginning
|
|
|
|
To stop the listener session above press: Ctrl+C
|
|
|
|
To start an interactive message producer session:
|
|
kubectl -n {{ .Release.Namespace }} exec -ti testclient -- kafka-console-producer --broker-list {{ include "common.fullname" . }}-headless:9092 --topic test1
|
|
|
|
To create a message in the above session, simply type the message and press "enter"
|
|
To end the producer session try: Ctrl+C
|
|
|
|
If you specify "zookeeper.connect" in configurationOverrides, please replace "{{ .Release.Name }}-zookeeper:2181" with the value of "zookeeper.connect", or you will get error.
|
|
|
|
{{ if .Values.external.enabled }}
|
|
### Connecting to Kafka from outside Kubernetes
|
|
|
|
You have enabled the external access feature of this chart.
|
|
|
|
**WARNING:** By default this feature allows Kafka clients outside Kubernetes to
|
|
connect to Kafka via NodePort(s) in `PLAINTEXT`.
|
|
|
|
Please see this chart's README.md for more details and guidance.
|
|
|
|
If you wish to connect to Kafka from outside please configure your external Kafka
|
|
clients to point at the following brokers. Please allow a few minutes for all
|
|
associated resources to become healthy.
|
|
{{ $fullName := include "common.fullname" . }}
|
|
{{- $replicas := .Values.replicas | int }}
|
|
{{- $servicePort := .Values.external.servicePort | int}}
|
|
{{- $root := . }}
|
|
{{- range $i, $e := until $replicas }}
|
|
{{- $externalListenerPort := add $root.Values.external.firstListenerPort $i }}
|
|
{{- if $root.Values.external.distinct }}
|
|
{{ printf "%s-%d.%s:%d" $root.Release.Name $i $root.Values.external.domain $servicePort | indent 2 }}
|
|
{{- else }}
|
|
{{ printf "%s.%s:%d" $root.Release.Name $root.Values.external.domain $externalListenerPort | indent 2 }}
|
|
{{- end }}
|
|
{{- end }}
|
|
{{- end }}
|