Documentation
¶
Overview ¶
Command mesh-dns is the standalone, slim mesh-DNS resolver binary run by the aether-mesh-dns DaemonSet (issues #578, #583).
It is intentionally self-contained: it imports ONLY the meshdns resolver and its direct deps (fsnotify, OTel push telemetry, cobra), and deliberately does NOT pull in the full agent (controller-runtime, go-control-plane/xDS, CNI, SPIRE). That keeps the binary — and its re-exec cost for the pod-local readiness probe — tiny, which is the entire point of #583 (and the CPU-reclaim half of #582): the readiness probe re-execs THIS binary to stat a pod-local marker, and a slim binary makes that cheap. The in-process httpGet probe #582 proposed is unsafe on a host-network + maxSurge DaemonSet (two pods share the host netns), so the provably-pod-local ready-marker exec probe from #580 is kept — this binary just makes it cheap.
It has no Kubernetes API access — records come only from the snapshot file the agent writes and this daemon watches via fsnotify.
Source Files