Deploy Loki in SingleBinary mode with retained filesystem storage

[Copilot]

Adds Loki as the log storage backend for the observability stack. Alloy is already configured to push to loki.observability-loki.svc.cluster.local:3100/loki/api/v1/push.

Configuration

• Deployment mode: SingleBinary with gateway disabled for direct access on port 3100
• Storage: 10Gi PVC with local-path-retain storage class, filesystem-based (no object storage dependency)
• Retention: 7 days (limits_config.retention_period: 168h)
• Schema: TSDB/v13 with 24h index period
• Auth: Disabled for internal cluster use
• Replication: Factor of 1 (single instance)

The service DNS and port match Alloy's existing configuration exactly, enabling immediate log ingestion on deployment.

Chart Details

• Official Grafana Loki chart v6.28.0
• Project: coachlight-k3s-observability
• Namespace: observability-loki
• Sync wave: 20 (consistent with platform services)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• grafana.com
  • Triggering command: /usr/bin/curl curl -s REDACTED (dns block)
• grafana.github.io
  • Triggering command: /usr/bin/curl curl -s REDACTED (dns block)
  • Triggering command: /usr/local/bin/helm helm repo add grafana REDACTED (dns block)
• https://api.github.com/repos/grafana/loki/contents/production/helm/loki/templates
  • Triggering command: /usr/bin/curl curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Deploy Loki (logs backend) with retained storage + Alloy ingestion</issue_title>
<issue_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

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Deploy Loki (logs backend) with retained storage + Alloy ingestion #162

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.