Bruno

Something like this: ```helm {{/* Common labels */}} {{- define "loki.labels" -}} app.kubernetes.io/name: {{ template "loki.name" . }} helm.sh/chart: {{ include "loki.chart" . }} app.kubernetes.io/managed-by: {{ .Release.Service }} app.kubernetes.io/instance: {{...

With this import, it's better: ```js import { Writer, Reader, Connection, SASL_PLAIN, SASL_SCRAM_SHA512, TLS_1_2 } from "k6/x/kafka"; // import kafka extension ```

Thanks

Now, I'm trying to test a listerner with SASL over TLS. I configure the tlsConfig.serverCaPem with the path of my CA file. ```js // TLS config is optional const tlsConfig...

But if my listerner does SASL authentication over TLS, I have only the CA. With CA, user cert & key, it is TLS authentication and not SASL authentication.

Here, you have an explanation of the difference between TLS 1 way and TLS 2 way. https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/ In your case, when you do SASL over TLS, you establish a TLS...

Hi @mostafa , I found this video which explains the difference between TLS and SASL over TLS. https://www.youtube.com/watch?v=_PmEs8xEz8g Rgds.

In the same context, it was possible to add custom rules in a configmap and set its name in this parameter: https://github.com/grafana/helm-charts/blob/loki-2.16.0/charts/loki/values.yaml#L342 Is it possible to keep this feature ?

Hi, Sorry for the delay to answer. I tested SASL auth, SASL auth over TLS, and TLS auth. All works fine. Thanks a lot. Rgds.

Hello, this is a good idea. But it would be nice to keep the compatibility with the current version (file path). For example, when you use k6 on Kubernetes, you...