TARE CLI

tare (Tetrate Agent Router) is a single-command operator tool for deploying the Agent Router data plane. It collapses three manual steps (image sync, pull-secret creation, and Helm deployment) into one invocation.

---

Commands

Command	Description
tare install	Install the Agent Router data plane
tare uninstall	Tear down the Agent Router data plane (cluster-only; reverses install)
tare upgrade	Upgrade an existing Agent Router data plane release (HA-safe, atomic)
tare gateway install	Install serve gateway resources (GCP, Azure, or AWS)
tare gateway config init	Generate a starter gcp-gateway.json from a domain and project ID
tare gateway config lint	Lint a gcp-gateway.json config (hermetic, CI-safe)
tare mcp install	Deploy MCP server pods on a customer cluster
tare mcp list	Show deployed MCP server status
tare mcp enable	Register a deployed MCP server in the management plane's MCP catalog
tare mcp uninstall	Remove the tars-mcp Helm release
tare integrate	Configure local coding tools (Claude Code, Codex, and others) against the Agent Router gateway

Quick start

# Print Helm values without touching the cluster
tare install identity.json --print-helm-values

# Full install
tare install identity.json

# Sync images to a private registry then install
tare install identity.json \
  --image-sync myregistry.example.com

# Sync + create pull secret + install in one command
echo "user:password" | tare install identity.json \
  --image-sync myregistry.example.com \
  --image-pull-secret-stdin

Identity file

tare accepts the service-account file in both formats produced by the management plane:

Wrapped format (standard):

{
  "serviceAccount": { ... },
  "checksum": "664b355c...",
  "checksumAlgorithm": "sha256"
}

Naked format (direct service account JSON):

{
  "type": "service_account",
  "clientEmail": "[email protected]",
  ...
}

Use tars sa wrap to convert a naked file to the wrapped format.

Gateway config schema

For tare gateway install, the config file shape depends on the provider:

• gcp-gateway.json schema: --type gcp
• azure-gateway.json schema: --type azure
• --type aws takes no config file; it is configured entirely by flags

Version

tare --version

Generated command reference

Every command has a generated reference page derived directly from its --help output, for example tare install. The generated pages carry the authoritative flag lists; the hand-authored pages in this section cover workflows, defaults, and troubleshooting.

---

Where to go next

tare install

Full reference for installing the data plane on a target cluster.

tare gateway config init

Generate a starter gateway config from a domain and project ID.