issue 130: undeclaring a service stops it, even one the mesh only reloads or keeps running #142

Merged
jschoubben merged 5 commits from issue/130-undeclaring-a-service-stops-it into main 2026-09-26 22:58:43 +00:00
Owner

Found reviewing the uplink modules (ADR 0117, #139): the host's remove path stops every undeclared service. Right for a service the mesh brought into being; wrong for a unit it only acts on. Live today: the private network's registry-trust-reload (docker.service — unassigning networking stops the container runtime) and the sshd module (unassigning it stops sshd). The uplink modules would have stopped the network manager.

Proposed: a service with no state — the unit's lifecycle is the machine's (being built on mesh-host #30 for the uplink modules); then move registry-trust-reload and sshd's service to it, and name units an undeclare will stop in a preview.

Found reviewing the uplink modules (ADR 0117, #139): the host's remove path stops every undeclared `service`. Right for a service the mesh brought into being; wrong for a unit it only acts on. Live today: the private network's `registry-trust-reload` (docker.service — unassigning networking stops the container runtime) and the sshd module (unassigning it stops sshd). The uplink modules would have stopped the network manager. Proposed: a service with no `state` — the unit's lifecycle is the machine's (being built on mesh-host #30 for the uplink modules); then move `registry-trust-reload` and sshd's service to it, and name units an undeclare will stop in a preview.
jschoubben added 5 commits 2026-09-26 22:58:20 +00:00
jschoubben force-pushed issue/130-undeclaring-a-service-stops-it from 92babaa919 to 248c99ca6c 2026-09-26 22:58:20 +00:00 Compare
jschoubben merged commit 762300a380 into main 2026-09-26 22:58:43 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#142