Skip to content

Plan / Interface: per-session Kata VM isolation for Kubernetes execution #2052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tgrunnagle wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Plan / Interface: per-session Kata VM isolation for Kubernetes execution #2052

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d5cd117
docs(plan): per-session Kata VM isolation for Kubernetes execution
tgrunnagle Oct 1, 2026
0a55073
docs(plan): link Plan / Interface PR #2052
tgrunnagle Oct 1, 2026
74e8e14
docs(plan): note operator hooks may be revisited under execution
tgrunnagle Oct 1, 2026
9d8e338
docs(adr): accept ADR 0373 on merge of #2052
tgrunnagle Oct 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/acceptance/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,6 +144,9 @@ PR after verification. There is no cleanup or status-only PR.
- [Native Kubernetes execution provider](native-kubernetes-execution.md) — separately deployed,
optional controller/executor service in this monorepo, with retained workspaces and kind
qualification. Status: draft; implementation is planned as a draft PR stacked on the plan PR.
- [Kubernetes session VM isolation](kubernetes-session-vm-isolation.md) — follow-up that runs each
native execution environment in its own Kata VM, keeps all session command execution out of the
mecak8s Pod, and stops the VM when the last reference is removed. Status: proposed.

- [Development-spine work classification](adr-scope-classification.md) — routes Spike,
Routine, Bounded, and Architectural work; keeps acceptance planning for substantive work
Expand Down
Loading
Loading