{{- /*
The broker image comes from kafka.brokerImage, which composes it from the
strimzi-kafka-operator values (defaultImageRegistry, defaultImageRepository, defaultImageTag)
and cluster.kafka.version, or from cluster.kafka.image when one is set. So these commands pull
the image the cluster actually runs. They used to name quay.io/strimzi/kafka:{{ .Version }}-...,
where .Version is the *chart dependency*
version - that pointed at the unpatched upstream image, on a registry a restricted or
air-gapped cluster cannot reach.
*/ -}}
{{- $kafkaImage := include "kafka.brokerImage" $ }}
Check pods:
kubectl get pod -n {{ .Release.Namespace }} --watch

Check strimzi operator logs:
kubectl logs deployment/strimzi-cluster-operator -n {{ .Release.Namespace }} -f

Check wait for kafka to deploy:
kubectl wait kafka/{{ .Values.cluster.name }} --for=condition=Ready --timeout=300s -n {{ .Release.Namespace }}

{{range .Chart.Dependencies }}
{{if eq .Name "strimzi-kafka-operator" }}
Write to topic:
kubectl -n {{ $.Release.Namespace }} run kafka-producer -ti --image={{ $kafkaImage }} --rm=true --restart=Never -- bin/kafka-console-producer.sh --bootstrap-server {{ $.Values.cluster.name }}-kafka-bootstrap:9092 --topic my-topic

Write read from topic:
kubectl -n {{ $.Release.Namespace }} run kafka-consumer -ti --image={{ $kafkaImage }} --rm=true --restart=Never -- bin/kafka-console-consumer.sh --bootstrap-server {{ $.Values.cluster.name }}-kafka-bootstrap:9092 --topic my-topic --from-beginning
{{end }}
{{end }}