Adds --disable-reporting to both Alloy releases (pod-log DaemonSet and alloy-syslog) via alloy.extraArgs, and INFLUXD_REPORTING_DISABLED=true to InfluxDB. Both currently try stats.grafana.org / telemetry.influxdata.com and are denied by egress policy. Alloy pods and the InfluxDB pod restart once.
Adds `--disable-reporting` to both Alloy releases (pod-log DaemonSet and alloy-syslog) via `alloy.extraArgs`, and `INFLUXD_REPORTING_DISABLED=true` to InfluxDB. Both currently try stats.grafana.org / telemetry.influxdata.com and are denied by egress policy. Alloy pods and the InfluxDB pod restart once.
S28-41
🤖 Generated with [Claude Code](https://claude.com/claude-code)
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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds
--disable-reportingto both Alloy releases (pod-log DaemonSet and alloy-syslog) viaalloy.extraArgs, andINFLUXD_REPORTING_DISABLED=trueto InfluxDB. Both currently try stats.grafana.org / telemetry.influxdata.com and are denied by egress policy. Alloy pods and the InfluxDB pod restart once.S28-41
🤖 Generated with Claude Code