Files
mesh-lab/scenarios/grafana-node.yml
T
jschoubben 5d6e8fbe7a Rename mesh-control -> mesh-controller, substrate -> foundation
One name per thing, per the HQ glossary: the module/container/image/binary/repo
becomes mesh-controller, the seat the-controller, and the store+broker pair the
foundation (embedded base bundles, default template and example lock renamed with
their go:embed directives). No behaviour change — a pure vocabulary rename.

Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
2026-09-16 18:40:40 +02:00

28 lines
823 B
YAML

# One machine that becomes a mesh and assigns itself grafana's tool runtime, configured by settings.
#
# plex/sonarr prove a runtime that self-detects its credential; this proves the other half of the
# config story (novox/hq ADR 0051 + 0052): the operator states grafana's URL and token as the
# assignment's settings, the mesh merges them into the config file the runtime reads, and the
# runtime registers and serves grafana's tools from that — no credential baked into the manifest.
scenario: grafana-node
segments:
hosting:
kind: public
cidr: [192.0.2.0/24]
machines:
anchor:
at: { segment: hosting, address: [192.0.2.10] }
egress: true
inbound: allow
memory: 3GiB
cpus: 2
images:
- mesh-controller:development
- mesh-runtime-grafana:development
place:
all: [host, runtime]