jschoubben
5c91c0ecd2
Every scenario that places a container runtime gives each of its machines `egress: true` — a node that runs modules pulls images from the internet, which is what a node does. The underlay-only scenarios (bootstrap-single, behind-nat, segmented-and-unforwardable, the-ordinary-shape, two-on-a-segment) stay sealed on purpose: an extra NIC would change the very reachability they are asserting about. `images:` keeps only the mesh's own — 55 third-party entries leave whole-mesh-full alone, and the machine fetches them itself by the digest its module.json already pins. The whole-mesh beds also say per machine which of ours they get: novox the substrate control plane and its own fifteen runtimes, ace its twenty-four, the two workstations one each. That is not a lab economy. An operator's workstation holds the images its own modules need, and giving these two the union would put some thirty gigabytes onto a thirty-gigabyte disk. bootstrap-with-registry.yml is deleted. It existed only to demonstrate the lab's registry, nothing referenced it, and there is nothing left for it to demonstrate. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
47 lines
2.3 KiB
YAML
47 lines
2.3 KiB
YAML
# One machine that becomes a mesh and is then assigned the route-proxy provider and a hello-web
|
|
# consumer — the bed that proves route-forwarding end to end (novox/hq ADR 0007,
|
|
# 08-connectivity §3 Exposure).
|
|
#
|
|
# **A route is a grant.** hello-web `requires: route` and contributes the name it wants and the port
|
|
# it listens on; route-proxy `provides: route`, is given every consumer as a file the mesh writes
|
|
# (`receives.route`), and forwards by the request's `Host` header to where the mesh says that
|
|
# consumer is. The sharp point this bed proves, straight from 08-connectivity §3's "Checked in the
|
|
# lab": a request to the consumer's name, sent to the proxy, reaches the workload and returns the
|
|
# workload's own answer — then unassigning the consumer withdraws the route and the same request
|
|
# stops working (the proxy replaces its table rather than merging).
|
|
#
|
|
# This bed proves the ROUTE-FORWARDING half over plain HTTP. The public-ACME/TLS half — ordering a
|
|
# publicly-trusted certificate and answering an HTTP-01 challenge at the name — is proven separately
|
|
# by certificates.test.ts against a real ACME server (Pebble), driving the same proxy binary.
|
|
#
|
|
# MESH_LAB_HOST_BINARY=.../mesh-host MESH_LAB_BUNDLE=.../examples/substrate-first-node.lock
|
|
# scripts/build-route-proxy-image.sh builds mesh-route-proxy:development into the local daemon
|
|
# (from mesh-control/examples/route-proxy, via mesh-catalog/modules/route-proxy/Dockerfile).
|
|
# alpine:latest must be in the local daemon — hello-web's backend is a bare alpine that serves a
|
|
# fixed page over a busybox nc loop. Both images are stocked and served by digest.
|
|
scenario: route-forwarding
|
|
|
|
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-control:development
|
|
# The route-proxy's image, built from the canonical Go proxy in mesh-control by
|
|
# scripts/build-route-proxy-image.sh, and hello-web's backend, a bare alpine nc loop.
|
|
- mesh-route-proxy:development
|
|
|
|
place:
|
|
# Only the host — neither module carries a mesh-runtime. Both service images are served by the
|
|
# internet and pulled by the host over its uplink, not placed inside the machine.
|
|
all: [host]
|