Deploy Loki (logs backend) with retained storage + Alloy ingestion #162
Description
Goal
Deploy Loki as the log storage/query backend for Grafana, receiving logs from Alloy.
Scope / Tasks
Create Argo CD Application:
argocd/apps/platform/loki.yml
Use the official Grafana Loki chart (not a “loki-stack” chart).
In valuesObject, set only overrides:
Persistence enabled for Loki components that require it (depending on deployment mode)
Storage class: use a Retain class for important logs (per your tiers)
Retention settings (minimal but explicit if required)
Ensure Alloy’s exporter points to Loki:
Service DNS name and port must match what Loki exposes internally
Acceptance Criteria
Loki is healthy and queryable from within the cluster
Grafana can add Loki datasource successfully (later issue will do this)
Alloy logs appear in Loki
Notes
If you choose “single binary” Loki for homelab simplicity, do that explicitly and document via issue comments; keep chart overrides minimal.
https://github.com/grafana/loki/tree/main/production/helm/loki
https://raw.githubusercontent.com/grafana/loki/refs/heads/main/production/helm/loki/values.yaml