claude-botandClaude Fable 5
8b1480f429
Closes the vantage-point gap that let the 2026-07-24 controller outage run ~20 h unnoticed: every existing probe of the public names resolves in-cluster (CoreDNS/k8s_gateway) or gets hairpinned, so nothing measured the actual WAN path. - blackbox module http_2xx_wan_edge: probes the edge by proxy IP literal with SNI/Host pinned to home.renner.uno. The Server/Ingress VLANs are deliberately absent from the UniFi hairpin, so IP-literal probes from the in-cluster exporter genuinely leave via the WAN and come back through the netcup edge (verified live from a pod: v4 returns 200; v6 currently fails against proxy-1 — real breakage, fixed separately by the resolv.conf PR). - New probes: WAN edge per member/family (proxy-2 v4, proxy-1 v6), https://netbird.renner.uno (controller), relay :9000/health on both netcup members, tcp :33080 relay listeners. - New PrometheusRule netbird-availability: controller unreachable (critical 10m), whole edge down from WAN (critical 5m), single edge member down (warning 15m), relay member down (warning 15m). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>