Infrastructure setup
Fill in the left-hand column:
| Field | What to enter |
|---|---|
| Deployment Type | Leave Partially Managed ( D2P ). The control plane stays in Trust3 Cloud and only the data plane runs in your environment. (Self-Managed, where you host the database and the control plane yourself, is a different install and is not covered here.) |
| Configuration Mode | Basic Config uses guided defaults. Advanced Config adds the Storage & Connectivity and Cloud Permissions steps. |
| Cloud Provider | Click the tile for the cloud your Kubernetes cluster runs in: AWS, Azure, or GCP. The prerequisites panel on the right changes to match. |
| Region | Pick the region your cluster is deployed in. |
| Runtime Name | Auto-filled as cloud-region-NNN, for example aws-us-east-1-871. Keep it or personalise it. |
About the runtime name¶
This name becomes the Kubernetes namespace, so it has rules:
- 6 to 44 characters
- lowercase letters, numbers, and hyphens only
- must start and end with a letter or number
The ↻ icon next to the field generates a fresh suggestion. If you type a custom region, it must be at least 7 characters and use the same character set, so that the generated name stays a valid namespace.
Pick the name deliberately
The name is used for the namespace and for internal service names, and it becomes part of the hostname of any endpoint the plane exposes. Renaming it later means recreating the runtime plane, so choose something you can live with — a short name that identifies the environment, such as prod-us-east-1 or aws-us-east-1-871.
Confirm the prerequisites¶
On the right-hand side is a checklist for the cloud provider you selected. Work through it and tick each item once it is true of your cluster.
| Item | What it means |
|---|---|
| EKS Cluster Configuration | Kubernetes v1.34+, r5.2xlarge nodes, 1–10 node auto-scaling. |
| Terminal Access to Cluster | You have terminal access to the EKS cluster to run kubectl and helm, with cluster-admin permissions. |
| Required Command-Line Tools | AWS CLI v2.12.0+, kubectl v1.34+, Helm v3.9.0+, and curl/wget are installed. |
| Kubernetes Metrics Server | Metrics Server is installed and running, for monitoring and autoscaling. |
| Item | What it means |
|---|---|
| AKS Cluster Configuration | Kubernetes v1.34+, Standard_E8s_v3 nodes, 1–10 node auto-scaling. |
| Terminal Access to Cluster | You have terminal access to the AKS cluster to run kubectl and helm, with cluster-admin permissions. |
| Required Command-Line Tools | Azure CLI v2.50.0+, kubectl v1.34+, Helm v3.9.0+, and curl/wget are installed. |
| Kubernetes Metrics Server | Metrics Server is installed and running, for monitoring and autoscaling. |
| Item | What it means |
|---|---|
| GKE Cluster Configuration | Kubernetes v1.34+, n2-standard-8 nodes or equivalent, node pool autoscaling 1–10 nodes. |
| Terminal Access to Cluster | Terminal access to run kubectl and Helm with Kubernetes Engine Cluster Admin or equivalent. |
| Required Command-Line Tools | Google Cloud SDK 450.0.0+, kubectl v1.34+, Helm v3.9.0+, and curl or wget. |
| Kubernetes Metrics Server | Metrics Server is installed and running, for monitoring and workload autoscaling. |
Two helpers sit alongside the list:
- Download Script — downloads a script that carries out the preparation steps for you.
- View full details — opens step-by-step manual instructions for that one item.
When every box is ticked, the panel shows All prerequisites confirmed and the button at the bottom of the page becomes available.