Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
make Agent Sandbox bullets single sentences
Jake Hulberg10054691b684
diff --git a/docs/documentation/platform/agent-vault/guides/kubernetes.mdx b/docs/documentation/platform/agent-vault/guides/kubernetes.mdxindex e165f4a153..9b68c00d2b 100644--- a/docs/documentation/platform/agent-vault/guides/kubernetes.mdx+++ b/docs/documentation/platform/agent-vault/guides/kubernetes.mdx@@ -62,8 +62,9 @@ For each agent run, your orchestrator does the following:<Accordion title="Can I use Agent Sandbox instead of writing pod manifests?">Yes. [Agent Sandbox](https://github.com/kubernetes-sigs/agent-sandbox) is an official Kubernetes project with custom resources for agent sandboxes, such as `SandboxTemplate`, `SandboxClaim`, and `SandboxWarmPool`. Its sandboxes are pods, so the proxy and the agents namespace work the same way, with these differences:- - **Session tokens:** each sandbox still needs its own session, but a `SandboxTemplate` serves every claim, so it can't name a per-run Secret. Your orchestrator has to deliver each sandbox's session token after the claim binds. Pods in a `SandboxWarmPool` start before any session exists.- - **Network policies:** if the Agent Sandbox controller creates its own network policy for a template, that policy can allow traffic that the agents namespace's policy blocks. Turn it off or limit it to the proxy, then check that a sandbox can't reach the internet directly (see [Verify it works](/documentation/platform/agent-vault/guides/kubernetes-setup#step-6-verify-it-works)).+ - **Session tokens:** a `SandboxTemplate` serves every claim, so your orchestrator has to deliver each sandbox's session token after its claim binds+ - **Warm pools:** pods in a `SandboxWarmPool` start before any session exists, so they also get their session token after the claim binds+ - **Network policies:** a network policy that the Agent Sandbox controller creates can allow traffic that the agents namespace's policy blocks, so turn it off or limit it to the proxy, then [check direct egress](/documentation/platform/agent-vault/guides/kubernetes-setup#step-6-verify-it-works)</Accordion></AccordionGroup>