Skip to content

RFC 0005: Platform-managed Kubernetes sandboxes#1680

Open
rohancmr wants to merge 1 commit into
NVIDIA:mainfrom
rohancmr:rfc/platform-managed-kubernetes-sandboxes
Open

RFC 0005: Platform-managed Kubernetes sandboxes#1680
rohancmr wants to merge 1 commit into
NVIDIA:mainfrom
rohancmr:rfc/platform-managed-kubernetes-sandboxes

Conversation

@rohancmr
Copy link
Copy Markdown

@rohancmr rohancmr commented Jun 2, 2026

Summary

Adds RFC 0005 for platform-managed Kubernetes sandbox provisioning.

This RFC proposes support for a trusted Kubernetes platform control plane to call OpenShell Gateway with a platform-selected namespace, supplied sandbox policy, approved Kubernetes Secret-backed provider credentials, runtime placement metadata, and optional Agent Sandbox allocation through SandboxClaim and SandboxWarmPool.

Related issue: #1678

Notes

  • RFC state is set to review.
  • This is a design proposal only; no runtime code changes are included.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 2, 2026

All contributors have signed the DCO ✍️ ✅
Posted by the DCO Assistant Lite bot.

Signed-off-by: Rohan Kumar <rohank@nvidia.com>
@rohancmr rohancmr force-pushed the rfc/platform-managed-kubernetes-sandboxes branch from 7119994 to 94b22ee Compare June 2, 2026 10:48
@rohancmr
Copy link
Copy Markdown
Author

rohancmr commented Jun 2, 2026

I have read the DCO document and I hereby sign the DCO.

@rohancmr
Copy link
Copy Markdown
Author

rohancmr commented Jun 2, 2026

recheck


### Request shape

The exact API can be protobuf-native, driver-specific configuration, or a
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean that we would add support through the proposal in #1589? (Or at least partially).

its configured default namespace. When the request namespace is omitted, the
driver keeps existing behavior and provisions into the configured namespace.

When the request namespace is present, the driver uses it as the namespace for
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This means it is still up to the user to specify the namespace, correct? How is access control to the namespace handled?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants