chore(security): scrub tailnet OTLP endpoint from defaults - #11
Conversation
Pre-publication prep: replace the internal tailnet OTLP hostname with localhost in compiled-in fallbacks, sample config, and chart values. Deployments supply the real endpoint via config/values overrides. Chart 0.1.0 -> 0.1.1.
🤖 Agent Jury — ✅ approved
SummaryReplaces the hardcoded tailnet OTLP endpoint with a localhost default across blackwall.toml, telemetry defaults, serve defaults/main, and Helm values, and bumps the Helm chart version to 0.1.1. No logic, control-flow, or input-handling changes are introduced, so no new defects are present. FindingsNo findings — the diff looks clean. Automated review by GLM-5.2 via LiteLLM gateway. Advisory — a human makes the final call. |
🤖 Agent Jury — ✅ approved
SummaryReplaces a hardcoded tailnet OTLP endpoint with localhost across Rust defaults, env-var fallback, config files, and Helm values; bumps chart version 0.1.0 to 0.1.1 and updates the corresponding test assertion. No logic, contract, or resource-handling changes are introduced; the only residual risk is that the localhost default will not resolve to a collector in a typical multi-pod Kubernetes deployment unless overridden or paired with a sidecar. FindingsNo findings — the diff looks clean. Automated review by GLM-5.2 via LiteLLM gateway. Advisory — a human makes the final call. |
1 participant
Pre-publication prep for the 2026-08-04 private→public batch (operator-authorized): internal tailnet OTLP hostname → localhost in compiled-in fallbacks, sample config, chart values. Chart 0.1.0→0.1.1. In-cluster k8s DNS names intentionally left as-is (functional defaults, low sensitivity).