fix(monitoring): turn off Alloy and InfluxDB usage telemetry

Both phone home on a timer: every alloy pod to stats.grafana.org (~135 a day each) and influxd to telemetry.influxdata.com (56 a day). Egress policy denies it, so this only removed log noise and wasted SYNs; switch it off at the source like Loki's reporting_enabled: false. --disable-reporting per the "alloy run" reference (chart alloy.extraArgs); INFLUXD_REPORTING_DISABLED per the InfluxDB v2 config options. S28-41 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 22:10:52 +01:00
3 changed files with 9 additions and 0 deletions
@@ -100,6 +100,9 @@ spec:
      # Keep tokens unhashed; enable hashing later as its own change.
      - name: INFLUXD_USE_HASHED_TOKENS
        value: "false"
+      # No usage telemetry to telemetry.influxdata.com (egress is denied).
+      - name: INFLUXD_REPORTING_DISABLED
+        value: "true"
    # The chart defaults to liveness/readiness with initialDelaySeconds=0,
    # so after a crash restart the kubelet kills the pod before shards
    # finish opening. Give it 10 minutes to come up cleanly.
@@ -54,6 +54,9 @@ spec:
      # non-RFC-framed payload). Scoped to this single-purpose receiver
      # only — the pod-log Alloy DaemonSet stays at default stability.
      stabilityLevel: experimental
+      # No usage reporting to stats.grafana.org (egress is denied anyway).
+      extraArgs:
+        - --disable-reporting
      resources:
        requests:
          cpu: 20m
@@ -116,6 +116,9 @@ spec:
      retries: 3
  values:
    alloy:
+      # No usage reporting to stats.grafana.org (egress is denied anyway).
+      extraArgs:
+        - --disable-reporting
      configMap:
        content: |
          // Discover and collect K8s pod logs