Issue 114: should the controller be a container or a process the host supervises #100

Closed

jschoubben wants to merge 2 commits from issue/113-controller-container-or-process into main

Author	SHA1	Message	Date
jschoubben	a97feeefe5	Renumber to 114: 113 collided with an issue merged independently to main Both used the next number available when opened, and the object-store withdrawal report merged first. No content change beyond the number.	2026-09-24 15:48:56 +02:00
jschoubben	a18550e460	Issue 113: should the controller be a container or a process the host supervises Filed after a session where every mesh-controller interaction went through docker exec — its manifest runs it as a container with network: host, using none of the isolation that resource type usually buys, while ADR 0006 makes it the mesh's single point of coordination. Open question, not a claimed defect: does type: container get the controller anything type: process (supervised the way the host supervises its own unit, per ADR 0005) would not.	2026-09-24 15:48:22 +02:00

Author

SHA1

Message

Date

jschoubben

a97feeefe5

Renumber to 114: 113 collided with an issue merged independently to main

Both used the next number available when opened, and the object-store
withdrawal report merged first. No content change beyond the number.

2026-09-24 15:48:56 +02:00

jschoubben

a18550e460

Issue 113: should the controller be a container or a process the host supervises

Filed after a session where every mesh-controller interaction went through
docker exec — its manifest runs it as a container with network: host, using
none of the isolation that resource type usually buys, while ADR 0006 makes
it the mesh's single point of coordination. Open question, not a claimed
defect: does type: container get the controller anything type: process
(supervised the way the host supervises its own unit, per ADR 0005) would not.

2026-09-24 15:48:22 +02:00