Files
MacLikorne 7ed80755f2 Chore/dev 947 upgrade loki (#332)
Co-authored-by: Benjamin Chastanier <benjamin.chastanier@gmail.com>
2021-10-01 14:12:52 +02:00
..
2020-10-30 17:28:54 +01:00
2021-10-01 14:12:52 +02:00
2021-10-01 14:12:52 +02:00
2021-10-01 14:12:52 +02:00

Loki Helm Chart

Prerequisites

Make sure you have Helm installed.

Get Repo Info

helm repo add grafana https://grafana.github.io/helm-charts
helm repo update

See helm repo for command documentation.

Deploy Loki only

helm upgrade --install loki grafana/loki

Run Loki behind https ingress

If Loki and Promtail are deployed on different clusters you can add an Ingress in front of Loki. By adding a certificate you create an https endpoint. For extra security enable basic authentication on the Ingress.

In Promtail set the following values to communicate with https and basic auth

loki:
  serviceScheme: https
  user: user
  password: pass

Sample helm template for ingress:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: loki
  annotations:
    kubernetes.io/ingress.class: {{ .Values.ingress.class }}
    ingress.kubernetes.io/auth-type: basic
    ingress.kubernetes.io/auth-secret: {{ .Values.ingress.basic.secret }}
spec:
  rules:
  - host: {{ .Values.ingress.host }}
    http:
      paths:
      - backend:
          service:
            name: loki
            port:
              number: 3100
        path: /
        pathType: Prefix
  tls:
  - hosts:
    - {{ .Values.ingress.host }}
    secretName: {{ .Values.ingress.cert }}

Use Loki Alerting

You can add your own alerting rules with alerting_groups in values.yaml. This will create a ConfigMap with your rules and additional volumes and mounts for Loki.

This does not enable the Loki ruler component which does the evaluation of your rules. The values.yaml file does contain a simple example. For more details take a look at the official alerting docs.