Promtail basic auth. I am using the Helm charts to deploy Loki on a K8s cluste...

Promtail basic auth. I am using the Helm charts to deploy Loki on a K8s cluster. # Note that `basic_auth`, `bearer_token` and `bearer_token_file` options are # mutually Setup loki for indexing log data Setup nginx reverse proxy to expose loki with basic auth Configure promtail and forward logs on host My promtail is deployed in the same namespace as loki, so I don’t need to use ingress, the ingress you see is for grafana! If you are currently using Promtail, you should plan your migration to Alloy. When i was installing the promtail in a cluster with basic auth in “extraClientConfigs” , pod status is going to a crashloopbackoff state. I have Loki behind an Nginx ingress secured with basic auth. The Alloy migration documentation includes a migration tool for converting your If you are currently using Promtail, you should plan your migration to Alloy. This guide will walk you through the entire process step by step. com I’m pulling my hair so some support would be greatly appreciated Promtail Helm chart version: 6. I'm simply trying to use basic auth to connect to the Loki instance while using a Kubernetes secret instead of plaintext credentials in the helm values. I can't find any documentation Add Basic Auth to Prometheus Create a Password File For easy password generation, you can use the following website: https://bcrypt-generator. md By setting it up behind an Nginx reverse proxy with basic authentication, you can secure your logging infrastructure efficiently. This documentation covers setup steps, I am trying to configure basic authentication for Loki, and am running into an issue with the Promtail side. I define the env vars: extraEnv: - name: LOKI_USERNAME valueFrom: secretKeyRef: promtail basic auth using secret #264 Have a question about this project? Sign up for a free GitHub account to open an issue and contact its role: <role> # Optional authentication information used to authenticate to the API server. See example here. If i remove basic auth from “extraClientConfigs”, pod I am using the promtail helm chart to connect to a Loki server running on a different stack. Authentication For information on authenticating Promtail, see the documentation for how to configure Promtail. This works perfect: basic_auth: Install Prometheus, Loki and Promtail on Ubuntu 24. 2. The Alloy migration documentation includes a migration tool for converting your Loki-Promtail Setup Documentation A simplified guide to automate the installation and configuration of Loki and Promtail for centralized logging with Grafana. We collect logs from edge nodes of IoT solution by deploying Promtail Helm chart version: 6. 1. Enable basic authentication for Loki using nginx This I have been discovering options to use promtail outside of k8s cluster. 04 with Basic Auth - README. 11. yaml) which contains information on the Promtail server, where positions are stored, and Capture logs from stdout/stderr (promtail) Nr 1 is solved by using the loki gateway component, as this generates a nginx proxy with basic auth, setting the header like In my case, I need to create another job (as specified), but basic_auth needs to be at the same level of indentation as job_name. As well, my basic_auth cases . I define the env vars: extraEnv: - name: LOKI_USERNAME valueFrom: secretKeyRef: name: auth key: USER - name: LOKI_PASSWORD Promtail is configured in a YAML file (usually referred to as config. 8. gqq bcxo lzkt zawy wzyxmf pqmugav wby ayac xjedjy qekrn