From f0aa9e5fed2cb4f69f518ec401396c2d81e94e67 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 25 Sep 2026 18:19:27 +0200 Subject: [PATCH] minio: declare the route contribution it has always needed, scoped from PR #58 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit files-api.novox.be and files.novox.be worked earlier tonight from route- adapter-generated files, but minio's module.json on main never actually carried a route requirement — that capability has been sitting in PR #58 the whole time, bundled with an unrelated network rename and console redirect URL that need their own calmer review. This is just the two routes: requires: route, contributes.route.api/.console (ContributesMany, proven working via mesh-controller #55/#57), and the console port (9001) actually published and declared in listens. Found assigning route-proxy for the first time tonight: its own routes file, generated the identical way route-adapter's always was, had four hostnames in it instead of six — nothing served files-api/files at all, which would have been a real, silent outage the moment Traefik stopped. --- modules/minio/module.json | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/modules/minio/module.json b/modules/minio/module.json index 8b1a05a..6a07e40 100644 --- a/modules/minio/module.json +++ b/modules/minio/module.json @@ -7,6 +7,21 @@ "scope": "mesh" } ], + "requires": [ + "route" + ], + "contributes": { + "route": { + "api": { + "label": "files-api", + "port": 9000 + }, + "console": { + "label": "files", + "port": 9001 + } + } + }, "capabilities": [ "container-runtime" ], @@ -20,6 +35,12 @@ "protocol": "tcp", "from": "mesh", "why": "the S3 endpoint" + }, + { + "port": 9001, + "protocol": "tcp", + "from": "mesh", + "why": "the admin console" } ], "serves": { @@ -92,7 +113,8 @@ "/var/lib/minio/root.env" ], "ports": [ - "9000" + "9000", + "9001" ], "volumes": [ "/var/lib/minio-store:/data", -- 2.54.0