From 2b5119ecd2dc29070f1fa9c2f5211cdb09b05a34 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 29 Sep 2026 22:38:11 +0200 Subject: [PATCH] Issue 114 is answered: the controller is a process, by ADR 0142 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It asked a question rather than reporting a defect, and the question was taken five days later — the mesh's own components are binaries on the machine, and third-party software stays a container because an image is the right way to carry somebody else's build. The delivery of them is issue 142. --- .../00-report.md | 22 +++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/04-ISSUES/114-should-the-controller-be-a-container-or-a-process/00-report.md b/04-ISSUES/114-should-the-controller-be-a-container-or-a-process/00-report.md index 6b03b96..194fbd7 100644 --- a/04-ISSUES/114-should-the-controller-be-a-container-or-a-process/00-report.md +++ b/04-ISSUES/114-should-the-controller-be-a-container-or-a-process/00-report.md @@ -1,8 +1,8 @@ --- -status: open +status: resolved opened: 2026-09-24 located-in: [mesh-controller module.json, mesh-host internal/apply] -fixed-by: +fixed-by: ADR 0142 — the mesh's own components are delivered as binaries on the machine, so the controller is a process; the delivery itself is issue 142 amended-design: --- @@ -84,3 +84,21 @@ restart and run-to-completion semantics — so this would not need host-side wor The two do not collapse into one. The controller is not a code-carrying sidecar, and `network: host` is what makes the asymmetry visible here and nowhere else. + +## Answered + +*2026-09-29, in a grooming pass.* This asked a question rather than reporting a defect, and the +question was taken: [ADR 0142](../../02-DECISIONS/0142-the-mesh-delivers-its-own-components-as-binaries.md) +decides that the mesh's own components — the host, the controller, the catalogue, the builder, the +vault — are **binaries on the machine**, delivered by the mechanism +[ADR 0141](../../02-DECISIONS/0141-the-host-delivers-its-own-successor.md) built, and that +third-party software (the store, the registry, the broker) stays a container because an image is the +right way to carry somebody else's build. + +So the operating experience this record was written from — every mutating command reached through +`docker exec mesh-controller` — is answered, and answered against the container. + +**The delivery is a separate matter and is not this record's.** Step 1 of it is built and no +component travels yet; that is +[issue 142](../142-the-host-is-the-one-thing-the-mesh-does-not-deliver/00-report.md). +