No container is given the mesh's names; it resolves them #161

2026-09-30T12:38:24Z

jschoubben commented

2026-09-30 12:38:24 +00:00

novox/hq ADR 0148 step 3: the roster leaves every container's declaration and so its digest. Resolves issues 109 and 151. One last recreation of every container follows the first push, since every digest loses its host entries; after that a name's blast radius is nothing.

jschoubben added 1 commit 2026-09-30 12:38:24 +00:00

No container is given the mesh's names; it resolves them c978aa7d64

novox/hq ADR 0148, step 3. Every container got the whole roster as
--add-host entries at creation and nothing re-read them (issues 109,
135); once the roster was in the digest so that could be caught, one
name moving anywhere replaced every container in the mesh (issue 151).
A container resolves through its machine's resolver, which the resolver
module tells the runtime about once per machine. A module's own hosts
entries stay exactly as declared.

Also brings the resolver tests up to the catalogue as it now is: the
runtime is reloaded (never restarted) and given live-restore, and the
resolver answers by address, not by interface (issue 110).

jschoubben merged commit d188eec318 into main

2026-09-30 12:38:27 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#161