Before You Begin¶
This page lists everything to have ready before you create a runtime plane, with the commands to set each piece up. The portal wizard (Settings → Runtime Plane) collects the same information and shows the same guidance in context.
Replace <placeholders> in the commands with your values. If you have not picked a deployment type yet, start with Deployment Options.
Trust3 AI Cloud planes need none of this
Everything on this page is about infrastructure you run. A Trust3 AI Cloud plane runs in Trust3AICloud, so there is nothing to prepare, nothing to install, and no wizard to complete — the only thing to confirm is that your data platforms accept connections from Trust3AICloud. Skip to Getting Started.
Kubernetes cluster¶
The cluster, command-line tools, and cluster add-ons you provide, per deployment type and cloud — plus how to verify terminal access and install the Metrics Server.
Kubernetes cluster prerequisites
Decisions to make¶
These apply to both deployment types:
| Decision | Details |
|---|---|
| Region | The cloud region where your cluster runs. |
| Runtime name | Auto-generated, but you can personalize it. It becomes the Kubernetes namespace for the runtime plane: lowercase letters, numbers, and hyphens only; 6–44 characters. The resource names below (trust3-<runtime-name>-role and similar) derive from it. |
| Auto Upgrade | On by default — the runtime plane follows the latest release. Turn it off if you want to pin a specific version. |
Deployment size¶
The CPU, memory and replica count every service starts with. Chosen once, when the plane is created, and fixed afterwards.
Storage, database, and secrets¶
Object storage, persistent volumes, the database, connector credentials, and AI Features — what each deployment type needs and the commands to create it.
Storage, database, and secrets
DNS and ingress¶
The ingress controller, DNS zone, TLS certificate, and load balancer settings that publish your service endpoints.
Cloud permissions¶
The IAM role, managed identity, or service account Trust3 assumes to reach your bucket, secret store, and DNS zone.
At deploy time¶
The portal shows the API key and private key for the runtime plane only once, together with the generated install commands (for Self-Managed, this includes the platform-bundle download). Have a secure place ready to store them before you start.
After running the install commands, verify all pods come up in Running state:
| Bash | |
|---|---|
- Prev topic: Deployment Options
- Next topic: Support Matrix