Deploy
Copy these now β they are shown only once
The page opens with a Security-Sensitive Configuration warning, and it means it. The installation commands contain your runtime plane's API key. Once you navigate away, the key is not displayed again, and getting a new one invalidates the old one.
Paste both commands somewhere safe before doing anything else β a password manager or your team's secret store, not a chat message.
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:
| Bash | |
|---|---|
The Helm command. It installs the runtime agent into your cluster, creating the namespace:
| Bash | |
|---|---|
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.
Save the API key separately if you plan to use custom agents
Click the eye icon on the download command and copy the value of the x-pcloud-key header. That value is your runtime plane's API key β the same string appears as --password in the Helm command.
You need it again when you publish a custom agent inventory with the Trust3 collector SDK β see the custom agents guide linked at the end of this page.
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:
- the
curl(orwget) command, which writesvalues.yamlinto your current directory - the
helm upgrade --installcommand, which deploys the runtime agent
Check that kubectl is pointed at the right cluster before you start:
| Bash | |
|---|---|
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:
| Bash | |
|---|---|
You are looking for a runtime-agent-β¦ pod in Running state.
Finish¶
- Click Done.
- 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.
- If you have saved the commands, tick I have saved the installation commands securely.
- 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:
| Bash | |
|---|---|