Skip to content

Agent Mesh

docs: call the control plane chart agentmesh

Tomas Tormoe1459030fb56
diff --git a/site/content/docs/concepts/architecture.md b/site/content/docs/concepts/architecture.md
index e0a8282a..15d382b1 100644
--- a/site/content/docs/concepts/architecture.md
+++ b/site/content/docs/concepts/architecture.md
@@ -159,7 +159,7 @@ The same three programs ship in several forms:
- **`agentmesh-one`**, a single binary that runs the control plane, a router and
the console in one process on one port, for laptops, Cloud Run and small
meshes.
-- **Helm charts**: `agentmesh-p2p` deploys the control plane, router, console and
+- **Helm charts**: `agentmesh` deploys the control plane, router, console and
PostgreSQL. `agentmesh-node` deploys a node beside a service container.
The web console (`agentmesh-console`) is a separate program that talks to the
diff --git a/site/content/docs/contributing/_index.md b/site/content/docs/contributing/_index.md
index 1ae807be..302727ef 100644
--- a/site/content/docs/contributing/_index.md
+++ b/site/content/docs/contributing/_index.md
@@ -21,7 +21,7 @@ in the repository has the details.
| `cmd/` | One directory per binary: `agentmesh-node`, `agentmesh-control-plane`, `agentmesh-router`, `agentmesh-one`, `agentmesh-console`, `mcp-client`, `agentmesh-bench`, and smaller tools. |
| `api/` | The wire contract: `agentmesh.proto` and its generated code, plus the Go types for the JSON admin API and the validation and Datalog helpers both sides share. |
| `internal/` | Implementation, one package per component (`node`, `controlplane`, `router`, `standalone`, `console`, `identity`, `storage`, ...). |
-| `charts/` | The `agentmesh-p2p` and `agentmesh-node` Helm charts. |
+| `charts/` | The `agentmesh` and `agentmesh-node` Helm charts. |
| `tests/integration/` | Go tests that start several components in one process. |
| `tests/e2e/` | Bats tests that drive the built binaries and containers. |
| `development/` | The kind environment and example services. |
diff --git a/site/content/docs/guides/kubernetes.md b/site/content/docs/guides/kubernetes.md
index 83e39602..2454048c 100644
--- a/site/content/docs/guides/kubernetes.md
+++ b/site/content/docs/guides/kubernetes.md
@@ -7,7 +7,7 @@ aliases:
---
This guide deploys a control plane, a router and a console into a cluster
-with the `agentmesh-p2p` Helm chart, then puts services on the mesh with the
+with the `agentmesh` Helm chart, then puts services on the mesh with the
`agentmesh-node` chart. The last section lists the settings to change when you
move from a test cluster to one that you keep. The public testnets run this
setup on GKE. Their manifests are in `.github/k8s/` in the repository.
diff --git a/site/content/docs/reference/router.md b/site/content/docs/reference/router.md
index c2b8eaf9..d78ef02f 100644
--- a/site/content/docs/reference/router.md
+++ b/site/content/docs/reference/router.md
@@ -25,7 +25,7 @@ A router enrolls like a node, requesting `mesh:role:router`, with one of:
| `--label` | A `key=value` label declared at enrollment, repeatable (`--label region=eu --label zone=eu-west1-b`). The control plane signs it only if `mesh:role:router` allows it in `allowed_labels`, lists it on `/info`, and nodes choose routers by it with `--router-selector` and `--router-prefer`. The same labels, with the same meaning, as a node's; see [labels](../../concepts/authorization/#labels). |
The mesh policy must bind the router's identity to `mesh:role:router`. The
-`agentmesh-p2p` Helm chart handles this: its bootstrap job binds the router's
+`agentmesh` Helm chart handles this: its bootstrap job binds the router's
service account and mints a bootstrap token with `max_usages` equal to the
replica count.