Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

move agent pod placeholders into bullets after the manifest

Jake Hulberg96f3b45e7f09
diff --git a/docs/documentation/platform/agent-vault/guides/kubernetes-setup.mdx b/docs/documentation/platform/agent-vault/guides/kubernetes-setup.mdx
index 5144ea2a00..48bafb39a5 100644
--- a/docs/documentation/platform/agent-vault/guides/kubernetes-setup.mdx
+++ b/docs/documentation/platform/agent-vault/guides/kubernetes-setup.mdx
@@ -253,7 +253,7 @@ For each agent run, your orchestrator does four things: creates a session, puts
### Define the agent's pod
-Save this manifest as `agent-pod.yaml`. Replace `<agent-image>` with your agent's image, and replace `<agent-command>` and `<argument>` with the command that starts your agent, with each argument as its own list item, such as `"claude", "-p", "Fix the failing test"`. Keep `<run-id>`, which the script in the next step fills in. The script gives each run a unique ID and uses it in the names of the run's pod and Secret and in its session's label:
+Save this manifest as `agent-pod.yaml`. The script in the next step starts a pod from it for each run:
```yaml expandable
apiVersion: v1
@@ -305,8 +305,11 @@ spec:
memory: 1Gi
```
+- **`<agent-image>`:** your agent's image
+- **`<agent-command>` and `<argument>`:** the command that starts your agent, with each argument as its own list item, such as `"claude", "-p", "Fix the failing test"`
+- **`<run-id>`:** leave it as is, because the script replaces it with a unique ID for each run
- **`infisical agent-vault run`:** fetches the proxy's certificate, then starts your agent with the proxy and [certificate trust](/documentation/platform/agent-vault/proxies#certificate-trust) variables set, so you don't install the certificate yourself (see the [CLI reference](/cli/reference#agent-vault-run))
-- **`runtimeClassName`:** picks the isolation level for the agent. Without it, the pod uses the standard runtime (see [Choose an isolation level](/documentation/platform/agent-vault/guides/kubernetes#choose-an-isolation-level))
+- **`runtimeClassName`:** picks the isolation level for the agent, and without it, the pod uses the standard runtime (see [Choose an isolation level](/documentation/platform/agent-vault/guides/kubernetes#choose-an-isolation-level))
- **`activeDeadlineSeconds`:** stops the agent after 30 minutes, so a stuck agent doesn't keep its session open
- **API keys in the agent's configuration:** delete the real keys, and pass a placeholder such as `agent-vault` to SDKs that won't start without one (see [Connect your own agent](/documentation/platform/agent-vault/guides/custom-agent#step-3-replace-the-api-keys-with-placeholders))