rfc-0005: propose sandbox proxy egress adapter model#1511
Draft
johntmyers wants to merge 4 commits into
Draft
Conversation
Signed-off-by: John Myers <johntmyers@users.noreply.github.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
2 tasks
drew
changed the title
drew
changed the title
jganoff
added a commit
to jganoff/OpenShell
that referenced
this pull request
Jun 24, 2026
Specify the Isolation Backend that RFC 0001 declared but left unspecified: the contract by which a pluggable backend establishes an agent's isolation boundary and the supervisor operates it, instead of the supervisor building the boundary inline with logic hardcoded for one environment. Why now: OpenShell is already building boundary placements other than in-pod (a microVM driver on main, open work for a node enforcer and an outer gVisor sandbox). Without a shared contract each one wires its own privileged setup and supervisor mode into the codebase. The interface makes them backends behind one contract instead of supervisor forks, and keeps open the path to a placement that runs the supervisor outside the agent's kernel without rewriting the supervisor. Contents: - Two-faces model: a provisioning contract the driver realizes on the control plane and a runtime contract the supervisor drives on the data plane, handing off through the provisioned environment. - An 8-call runtime contract with ordering as a security property; five calls stable, three (exec, port_forward, identity) provisional, validated only where the supervisor shares the agent's kernel. - A Scope-and-status section stating what is stable vs in flight, which placements share the kernel, that Phase 1 ships a consistency check rather than cryptographic verification, and a falsifiability clause. - Trust defined as a contract (four MUSTs); the cryptographic mechanism deferred to a Phase 2 trust RFC. Capability-gated identity with an assurance ladder. - A kernel-sharing 2x2 with the forbidden cell (one pod plus a kernel-separated supervisor is not expressible on stock Kubernetes), grounded in the CRI shape. - An in-pod-first, behavior-preserving implementation plan; the nft fail-open fix is a hard prerequisite for Phase 1. - Security disclosures (shared-kernel residual risk, init-container exposure) and explicit non-goals (control-plane authorization, the trust mechanism, one-to-N supervisors). Supporting files: topology-matrix.md (placement catalog + selection matrix), codebase-grounding.md (file:line verification against main). Refs NVIDIA#1737, NVIDIA#899, NVIDIA#981, NVIDIA#1511, NVIDIA#1650, NVIDIA#1680.
Signed-off-by: John Myers <johntmyers@users.noreply.github.com>
Signed-off-by: John Myers <johntmyers@users.noreply.github.com>
Signed-off-by: John Myers <johntmyers@users.noreply.github.com>
|
🌿 Preview your docs: https://nvidia-preview-pr-1511.docs.buildwithfern.com/openshell |
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
3 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.
Summary
Proposes an RFC for remodeling sandbox proxy egress around transport adapters, a shared egress intent/decision boundary, and relay-owned protocol parsing/dialing.
Related Issue
None.
Changes
Testing
mise run pre-commitpassesNot run; RFC/documentation draft only. A pre-commit run was started and then intentionally stopped because this is a draft RFC.
Checklist