jschoubben
86ea181c76
Thirty modules the mesh builds, provisions and runs, as manifests — one per module, flat under modules/. They were in mesh-control/examples/, which framed the mesh's real modules as illustrations of a control-plane package; they are neither examples nor the control plane's. The engine that reads them stays in mesh-control; the data lives here, consumed as a build source. Answers the tier-4 question novox/hq ADR 0030 left open — where the catalogue lives — in favour of one flat repository, which the drop of domain grouping (seats, claims and tags instead) makes the right shape. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
37 lines
759 B
JSON
37 lines
759 B
JSON
{
|
|
"module": "portainer",
|
|
"version": "1",
|
|
"capabilities": [
|
|
"container-runtime"
|
|
],
|
|
"listens": [
|
|
{
|
|
"port": 9443,
|
|
"protocol": "tcp",
|
|
"from": "mesh",
|
|
"why": "the container dashboard, over its own tls"
|
|
}
|
|
],
|
|
"resources": [
|
|
{
|
|
"id": "data",
|
|
"type": "directory",
|
|
"path": "/services/portainer/data",
|
|
"mode": "0700"
|
|
},
|
|
{
|
|
"id": "server",
|
|
"type": "container",
|
|
"name": "portainer",
|
|
"image": "portainer/portainer-ce@sha256:511f3f06c96fe3b993ebeaafde311c1959cae73a7ef825dba6397d51b450dffa",
|
|
"ports": [
|
|
"9443"
|
|
],
|
|
"volumes": [
|
|
"/services/portainer/data:/data",
|
|
"/var/run/docker.sock:/var/run/docker.sock"
|
|
]
|
|
}
|
|
]
|
|
}
|