Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
charts: trim the sam-node README
Tomas Tormofec638e08c42
diff --git a/charts/sam-node/README.md b/charts/sam-node/README.mdindex 6c1f7893..5fc26ee2 100644--- a/charts/sam-node/README.md+++ b/charts/sam-node/README.md@@ -31,19 +31,6 @@ service:image: calc-mcp:local```-Values files stack: keep environment wiring (`controlPlaneUrl`, extra args)-in a base file and the service description in its own, then pass both:-`helm install calc charts/sam-node -f base.yaml -f calc/values.yaml`-(later files win). The kind dev mesh ships such a base at-`development/kind/sam-node.values.yaml`.--The service container and the node share the pod's network, so `target_url`-points at `127.0.0.1:<port>`. Services declared in `config.services` are-advertised to the mesh via DHT and gossip; `config.attenuation` narrows what-the node's credential permits. Your `config` values are merged over the chart's-defaults and rendered as `sam-node.yaml` at startup — the chart rolls the pods-on config changes (checksum annotation).-## Values| Key | Default | Meaning |@@ -53,16 +40,8 @@ on config changes (checksum annotation).| `apiToken` | `devtoken` | Bearer token for the node's local REST API || `bindAddr` | `127.0.0.1:8080` | Node API bind address (loopback = pod-private) || `extraArgs` | `[]` | Extra sam-node args |-| `config` | empty services | Merged over the chart's defaults and rendered as `sam-node.yaml` |+| `config` | empty services | Merged over the chart's defaults and rendered as `sam-node.yaml`; pods roll on config changes || `service.image` | `""` | Service container image; empty = bare node || `service.name/command/env/ports/resources` | — | Service container spec || `image.repository/tag/pullPolicy` | `sam-node:local` | Node image || `replicaCount` | `1` | Each replica enrolls as its own mesh node |--## Dynamic registration (alternative to `config.services`)--A running node also accepts `POST /sam/service/register` on its API-(`bindAddr`, bearer `apiToken`) with a JSON body-`{"service":{"type":"mcp","name":"x","description":"…"},"targetUrl":"http://…"}`.-Registrations are in-memory: after a node restart the registrar must-re-register. Static `config.services` entries need no such care.