mesh-controller

Archived

This repository has been archived on 2026-11-02. You can view files and clone it. You cannot open issues or pull requests or push a commit.

Files

T

History

jschoubben b36f822cb6 Facts carry the format as a template, so the control plane holds none (ADR 0120)

A roster fact used to be a name from a closed list, each formatted in Go
here — node-names as a hosts file, node-zones as a resolver's zones. Every
new consumer (ssh's known_hosts, an authorized_keys) meant another formatter
in the control plane, in the consumer's own configuration language.

Now a fact is a path and a Go template over the roster view (this node, the
suffix, and every served name vs the machines). The mesh owns the data; the
module owns the format. /etc/hosts is a template on the network module;
dnsmasq's zones move to dnsmasq. The controller renders and reads neither.

WireGuard stays a computed generator: the overlay is the substrate delivery
rides on, and its config is topology, not a roster projection.

Output is byte-for-byte unchanged, pinned by the hosts golden tests and the
resolver tests that compose the real dnsmasq manifest.

2026-09-27 01:33:20 +02:00

declaration_test.go

The mesh's interface takes over the found tunnel's MTU

2026-09-26 22:40:42 +02:00

declaration.go

The mesh's interface takes over the found tunnel's MTU

2026-09-26 22:40:42 +02:00

generator_test.go

Write the registry's trust into the runtime's file and reload the runtime instead of restarting it; prefix reload-on like restart-on (hq ADR 0102)

2026-09-22 17:51:38 +02:00

generator.go

Facts carry the format as a template, so the control plane holds none (ADR 0120)