Runtime plane — basic setup¶

The shortest path to a working runtime plane: two form pages, two commands, done. This is the right choice for most first-time installs.

Before you start, work through Before you begin on the overview page — a cluster that meets the requirements, kubectl and helm access to it, and the Account Admin role in the portal.

If you need object storage, your own DNS name, a specific secret store, or you are setting up monitoring for custom agents, use Advanced setup instead.

Step 1 — Open the Create Runtime Plane page¶

1. Log in to the Trust3 AI portal.
2. In the left sidebar, click Settings.
3. In the Settings menu, click Runtime.

You are now on Runtime Environments. Any runtime planes you already have are listed here as cards, each showing its name, its type, a status badge such as Running, and when it last reported in. A fresh account normally shows one entry, Trust3 AI Cloud, which is the Trust3-hosted SaaS environment.

1. Click + Create New.

Step 2 — Fill in Infrastructure Setup¶

The Create Runtime Plane page opens on step 1 of 2, Infrastructure Setup. Leave Configuration Mode on Basic Config — that is what keeps the wizard to two steps.

Fill in the left-hand column:

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.

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.

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.

Click Generate.

Step 3 — Deploy¶

The Deploy step shows two commands.

The download command. Use the CURL tab, or the WGET tab if you prefer wget. It downloads a values.yaml for your runtime plane:

1
2
3

curl -fsSX GET https://<your-trust3-host>/runtime/runtime-plane/<id>/values/download \
  -H "x-pcloud-key: <your-api-key>" \
  -o values.yaml

The Helm command. It installs the runtime agent into your cluster, creating the namespace:

1
2
3
4
5
6
7

helm upgrade --install <runtime-name> https://<your-trust3-host>/runtime/helm/runtime-agent-1.0.0.tgz \
  --username trust3ai \
  --password <your-api-key> \
  --pass-credentials \
  --namespace <runtime-name> \
  --create-namespace \
  ...

Each block has two icons in its top-right corner:

• 📋 copy — copies the command, including the real credential values.
• 👁 eye — reveals the masked values on screen.

There is also a What this command does link next to each, if you want to know exactly what you are about to run.

Run the commands on your cluster¶

Open a terminal that is connected to your Kubernetes cluster — the one where kubectl is configured and working — and run the two commands in order, exactly as shown:

1. the curl (or wget) command, which writes values.yaml into your current directory
2. the helm upgrade --install command, which deploys the runtime agent

Check that kubectl is pointed at the right cluster before you start:

1

kubectl config current-context

Wait for the runtime agent to connect¶

Back in the portal, below the commands, you will see Waiting for Runtime Agent to connect…

You do not have to sit on this page. As the message says, you can close the window and finish later; the connection is established automatically once the commands have run.

Once the runtime agent pod is up and has called home, the status changes to connected.

To watch it from your side:

1

kubectl get pods -n <runtime-name>

You are looking for a runtime-agent-… pod in Running state.

Finish¶

1. Click Done.
2. A dialog appears — Don't lose access to your runtime — reminding you that these commands are how you reach the runtime plane via the instance CLI, and that without them you will have to regenerate access.
3. If you have saved the commands, tick I have saved the installation commands securely.
4. Click Leave Anyway.

Choose Stay on Page instead if you still need to copy something.

Verify¶

Go back to Settings → Runtime. Your new runtime plane should be listed with a Running status badge and a recent timestamp.

From the cluster side:

1

kubectl get pods -n <runtime-name>

What to do next¶

Open the runtime plane from Settings → Runtime and use its tabs to configure it:

• Collectors — add an AI Assets Collector and point it at your data sources or agents. See Run Collector.
• Configuration — review or change plane-level settings after creation. Anything you skipped by choosing Basic — storage, DNS, ingress — can be added here.

If you are here to govern agents you built yourself, continue with Monitoring custom agents.

Troubleshooting¶

1
2

kubectl get pods -n <runtime-name>
kubectl describe pod -n <runtime-name> -l app=runtime-agent