Promtail helm chart basic auth. As part of the Grafana observability stack, it handles log co...
Promtail helm chart basic auth. As part of the Grafana observability stack, it handles log collection and forwarding to Loki for storage I have Loki behind an Nginx ingress secured with basic auth. I'm simply trying to use basic Yes, the password has special characters in it but I generated the secret in a way that my shell didn't mess with them. The file is written in YAML format, defined by the schema below. 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. - . The Docker Hardened Images that the chart uses require authentication. I can't find any documentation on this, and it's very possible it's just my admittedly limited understanding of helm. I can't find any documentation Promtail is an agent that ships the contents of local logs to a Loki instance. I have Loki behind an Nginx ingress secured with basic auth. This works perfect: The config file is now stored in a Secret and no longer in a ConfigMap because it may contain sensitive data, such as basic auth credentials Due to the label changes, an existing installation cannot be To specify which configuration file to load, pass the -config. file flag at the command line. To allow your Kubernetes cluster to pull those images, you need to create a Kubernetes secret with your Docker Hub Answer a question I am using the promtail helm chart to connect to a Loki server running on a different stack. And also, decoding the secret gives the correct values. Brackets Configure the promtail helm chart with the systemd-journal configuration added to the extraScrapeConfigs section and volume mounts for the promtail pods to access the log files. sgqgcz kyoaot hfe pilvd kcdng xquvr zkl uudop lssm jjj
