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.

jschoubben 2277583e99 Tell the resolver the machines, not the names the mesh merely serves ...

The map the control plane hands a resolution holds both: the machines, and every name
the mesh was told to route to whichever machine serves it. A container's hosts wants all
of it, so a routed name resolves to the proxy. A resolver's zones want only the machines:
told the mesh's suffix is its own it answers authoritatively for everything under it and
forwards none of it, so a routed name with the suffix appended — drive.example.test.internal
— is a name nobody will ever ask for, standing beside the machines and looking as real.

Found composing the resolver's first assignment on a live machine, before pushing it.
hq issue 111.

2026-09-24 01:31:11 +02:00

..

mesh-builder

The control plane's recipe starts FROM the base its manifest declares, and an undeclared base is refused

2026-09-21 22:16:10 +02:00

mesh-controller

Tell the resolver the machines, not the names the mesh merely serves

2026-09-24 01:31:11 +02:00