Practical Notes
- Setup time ~30 minutes (apply manifests + run one sandboxed job)
- Three hard checks: limits enforced, egress scoped, run logs retained
- GitHub stars + forks (verified): see Source & Thanks
Agents get dangerous when they can run arbitrary code with long-lived credentials. A Kubernetes sandbox lets you bound blast radius: small quotas, short-lived identities, and auditable logs. Use it to make ‘agent execution’ an infrastructure primitive rather than an ad-hoc local script.
FAQ
Q: Do I need Kubernetes for agents? A: Not always—but it’s a strong default if you must isolate untrusted execution.
Q: What’s the first guardrail to add? A: Resource limits + restricted service accounts; then add egress controls.
Q: How do I make runs reproducible? A: Pin images/versions and treat manifests as code reviewed like any PR.