Skip to content

Getting Started with Runtime Plane

Most setup is in the portal (Settings → Runtime Plane): create the runtime plane, configure connectors, and follow the on-screen steps. This page summarizes how the runtime behaves and what you might do outside the form — without repeating field-level help the UI already provides.

How configuration and status move

Direction What happens
You → portal You enter runtime plane and connector settings.
Agent → Runtime Manager The agent polls for configuration and pushes status (agent health and connector state) to Runtime Manager.
Agent ↔ connectors The agent manages connector workloads. Connectors poll the agent for updates to the configuration properties they consume.

One-time secrets

When the runtime plane is created, the portal shows secrets only once (for example the Runtime Agent API key and the private encryption key for connector fields). Copy them safely before closing the dialog; they are not shown in full again except a new API key after Regenerate. How Sensitive Data is Handled explains Trust3AI Managed keys, where connector secrets can live (Trust3AI Cloud vs Kubernetes vs cloud native), and how they are protected; those credentials and connector secrets are consumed during provisioning and runtime according to your deployment.

Provisioning the Runtime Agent

Provisioning is portal-guided. Create the runtime plane in Settings → Runtime Plane, choose the deployment type, and the portal generates the exact commands to run against your Kubernetes cluster. See Deployment Options for how the two types differ.

  • Partially Managed (D2P) — The portal generates a values download and a Helm command that installs the Runtime Agent into your namespace. The agent then connects to the Trust3AI-managed control plane.
  • Self-Managed — The portal wizard collects your infrastructure, storage and connectivity, and cloud permissions, then generates the values and platform-bundle downloads and a Helm command that installs the full stack into your EKS cluster. When the pods are running, open your in-cluster portal.

After the runtime plane is live

  • When the runtime plane is Active, open it in the portal and provision connectors from the Connector tab.
  • For runtime plane and connector configuration changes and health, use the Trust3AI portal.
  • Change runtime plane and connector settings in the portal; the agent reconciles them and connectors pick up property updates by polling the agent.
  • To troubleshoot pods and check logs, use the Kubernetes cluster.