Gateway installation overview
Gateway resources expose and manage AI traffic to the data plane. The tare install-gateway command and its workflow come first; Tetrate Agent Router-specific runbooks follow.
Synopsis
tare install-gateway <identity-file> [flags]
Description
The tare install-gateway command deploys the gateway Helm chart required to expose Agent Router serve traffic. It manages the lifecycle of the gateway resources, from prerequisite validation to final DNS configuration guidance.
High-level workflow
- Identity loading: Validates and loads the provided
<identity-file>. - Configuration merging: Loads the optional
gcp-gateway.jsonvia--configand resolves values across flags, config, and identity defaults. - Prerequisite handling: Runs optional prerequisite workflows with
--dry-run-prereqsor--apply-prereqs. - Preflight validation: Verifies environment readiness.
- Installation: Deploys the Agent Router gateway chart through the embedded Helm engine.
- Finalization: Optionally waits for the Gateway address (
--wait) and outputs the required DNS A-record actions.
Provider support
| Provider | Status |
|---|---|
| Google Cloud Platform (GCP) | Fully supported |
| Azure Kubernetes Service (AKS) | Fully supported |
| Amazon Web Services (AWS) | Fully supported |
The AWS path is ingress-only and takes no config file. Instead of deploying the gateway chart, it exposes the data plane's egress as a Network Load Balancer by patching the egress EnvoyProxy, so no AWS Load Balancer Controller and no aws CLI are required.
Clusters outside AWS, GCP, and Azure
On a self-managed cluster there is no provider for tare install-gateway to drive, and the gateway is exposed through the cluster's own edge instead, typically an Ingress controller. The full path, including the Service pinning, namespace, and NetworkPolicy details, is in Expose the gateway on a generic cluster.
Where to go next
Gateway installation on GCP
Install the Agent Router gateway in a Google Cloud project using the tare CLI.
Gateway installation on AKS
Install the Agent Router gateway on Azure Kubernetes Service using the tare CLI.
Gateway installation on EKS
Expose the data plane on Amazon EKS as a Network Load Balancer using the tare CLI.