Data Plane Installation
The data plane (the Controller and the Agent Router) is installed into a Kubernetes cluster and connected to the management plane. The guides below differ by target cloud and installation tooling: Azure, AWS, GCP, or cloud-agnostic Helm.
Prerequisites
Every guide assumes three things are already in place:
- The prerequisites confirmed: access, accounts, cloud quotas, and network rules.
- Management plane onboarding complete through Step 5, which produces the data plane credential (
service-account.json). Once the data plane is running, that credential is rotated and revoked through the procedures in Data plane credentials. - A provisioned Kubernetes cluster meeting the Kubernetes version requirement. Cluster provisioning is not covered by Tetrate support.
Select a guide
Azure using tare CLI
Azure Kubernetes Service (AKS) using the tare CLI, the recommended AKS path where the CLI is available.
Azure installation guide →Azure using Helm
AKS using Helm, for environments that require a private container registry such as Azure Container Registry.
Azure Helm guide →AWS using tare CLI
Amazon Elastic Kubernetes Service (EKS) using the tare CLI.
AWS installation guide →GCP using tare CLI
Google Kubernetes Engine (GKE) using the tare CLI.
GCP installation guide →Helm (cloud-agnostic)
Any Kubernetes cluster, for platform teams that own the Helm release lifecycle and maintain a private container registry (Harbor, JFrog Artifactory, Nexus, or Google Artifact Registry).
Helm installation guide →Companion workflow
Where to go next