Data plane installation
The data plane is a Kubernetes deployment containing the Controller and the Agent Router. This step installs those components in the target cluster and connects them to the management plane. Select the guide that matches the target cloud platform and preferred installation tooling.
Select a guide
Azure using tare CLI
Install on Azure Kubernetes Service using the tare CLI. The recommended path for AKS deployments when the tare CLI is available in the environment.
Azure installation guide →Azure using Helm
Install on Azure Kubernetes Service using Helm and a private container registry such as Azure Container Registry. Use this guide when a private registry is required by the environment.
Azure Helm guide →AWS using tare CLI
Install on Amazon Elastic Kubernetes Service using the tare CLI.
AWS installation guide →GCP using tare CLI
Install on Google Kubernetes Engine using the tare CLI.
GCP installation guide →Helm (cloud-agnostic)
Helm-based installation for platform teams that own the Helm release lifecycle and maintain a private container registry such as Harbor, JFrog Artifactory, Nexus, or Google Artifact Registry.
Helm installation guide →Before you begin
All data plane guides assume the following steps are already complete:
- Prerequisites confirmed: access, accounts, cloud quotas, and network rules.
- Management plane onboarding complete through Step 5: organization details, providers, models, and the data plane credential (
service-account.json). - Target Kubernetes cluster provisioned and meeting the Kubernetes version requirement. Cluster provisioning is not covered by Tetrate support.
SSO is not required before data plane installation. Configure SSO after the gateway is running and before opening the Console to developers — see SSO configuration.
After installation
Gateway installation
Next step: install the data plane gateway components that manage inbound access and configure request routing.
SSO configuration
After the gateway is running, connect an OIDC identity provider before developer handoff.
Console quickstart
Once SSO is working and the gateway is reachable, issue an API key and make a first routed request from the Console.