Add idea: stronger workload isolation for agent workloads#6
Merged
rkoster merged 1 commit intoJul 8, 2026
Merged
Conversation
rrashidov
requested review from
beyhan,
itsouvalas,
rkoster and
wayneeseguin
as code owners
This was referenced Jul 8, 2026
rkoster
approved these changes
Jul 8, 2026
Contributor
|
@rrashidov Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this idea about?
Agent workloads run instructions chosen at inference time — the code that executes is not something a developer reviewed. A shared kernel with other tenants is a meaningful attack surface that traditional apps don't expose in the same way.
The proposal: CF should offer a gVisor-backed runtime option for agent workloads, surfaced as a manifest field (
runtime: sandbox) that opts the app into a user-space kernel boundary without changing how the app is pushed, scaled, or observed. Operator policy could make it the default for orgs hosting agent workloads. The CF implementation is left open for platform experts to propose.Grounded in the research already captured in PR #4 (
research/k8s-agent-sandbox.md), which documents how k8s-sigs decouples isolation mechanism from workload API viaruntimeClassName.Checklist
ideas/with a lowercase kebab-case filename (ideas/stronger-workload-isolation-for-agents.md)title:present)sandboxing-isolation,runtime-lifecycle)research/k8s-agent-sandbox.md, PR Add research note: Kubernetes Agent Sandbox (k8s-sigs) #4)Related
research/k8s-agent-sandbox.mdideas/localhost-only-egress-for-agents.mdideas/credential-less-agent-processes.md