TARE CLI

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

---

Commands

Command	Description
tare install	Install the TARS dataplane
tare uninstall	Tear down the TARS dataplane (cluster-only; reverses install)
tare upgrade	Upgrade an existing TARS dataplane release (HA-safe, atomic)
tare gateway install	Install serve gateway resources (GCP)
tare gateway config init	Generate a starter gcp-gateway.json from a domain + 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 fraser's catalog
tare mcp uninstall	Remove the tars-mcp Helm release

Quick start

# Print Helm values without touching the cluster
tare install identity.json --serve-url https://proxy.acme.com --print-helm-values

# Full install
tare install identity.json --serve-url https://proxy.acme.com

# Sync images to a private registry then install
tare install identity.json --serve-url https://proxy.acme.com \
  --image-sync myregistry.example.com

# Sync + create pull secret + install in one command
echo "user:password" | tare install identity.json \
  --serve-url https://proxy.acme.com \
  --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

Version

tare --version

CLI reference docs

The docs/tare/cli/ref/ directory contains auto-generated per-command reference files derived directly from each command's --help output.

Regenerate after any flag or help-text change:

make cli.docs

CI verifies the directory is up to date on every PR:

make cli.docs && git diff --exit-code docs/tare/cli/ref/

make cli.docs depends on cli.embed-charts and cli.manifest (both run automatically as prerequisites). The generator binary lives at svc/cli/cmd/tare-docgen.

---

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.