Skip to content

feat: Add NVIDIA OpenShell AI Agent Sandbox as Layer 2 Use Case - #191

Open
avijra wants to merge 1 commit into
validatedpatterns:mainfrom
avijra:feat/openshell-ai-agent-sandbox
Open

avijra wants to merge 1 commit into
validatedpatterns:mainfrom
avijra:feat/openshell-ai-agent-sandbox

Conversation

@avijra

@avijra avijra commented Nov 2, 2026

Copy link
Copy Markdown

Summary

Adds NVIDIA OpenShell as an opt-in Layer 2 use case, demonstrating zero trust for AI coding agents on top of the ZTVP foundation.

Closes #190

What's Included

File Purpose
charts/openshell-ztm/ Helm chart wrapping the official NVIDIA OpenShell subchart with ZTVP integrations
values-hub.yaml Commented-out opt-in entries (namespace + application)
values-secret.yaml.template MAAS API key secret entry

ZTVP Integration

The chart integrates with all 5 ZTVP pillars:

Pillar Integration
Vault + ESO API keys stored in Vault at hub/infra/openshell/maas, synced via ExternalSecret
Keycloak openshell-gateway OIDC client registered via KeycloakRealmImport in ztvp realm
SPIFFE/SPIRE ClusterSPIFFEID issued to the Gateway pod
ACS Continuous vulnerability scanning of sandbox container image
OpenShell Landlock LSM filesystem enforcement, allowlist-only network policy, credential boundary resolution

Zero Trust Capabilities

  • Network: Only 3 allowed hosts (MAAS LLM, npm, GitHub). Everything else denied in ~2ms.
  • Filesystem: Landlock LSM kernel enforcement. Only /sandbox and /tmp writable.
  • Credentials: Real API keys never enter sandbox. Resolver tokens swapped at network boundary.
  • Binary-level enforcement: Per-endpoint binary allowlists (curl, node, npm).
  • Dynamic policy: Live updates via openshell policy update — no restart needed.

How to Enable

  1. Uncomment the openshell-system namespace in values-hub.yaml
  2. Uncomment the openshell-ztm application entry in values-hub.yaml
  3. Uncomment the openshell-maas secret in values-secret.yaml.template
  4. Store your MAAS API key: echo -n "sk-..." > ~/.config/validated-patterns/maas-api-key
  5. Push and let ArgoCD reconcile

Testing

  • 3 complete E2E walkthroughs on ROSA 4.22 (OCP 4.22.19) + full ZTVP deployment
  • Chart v1.3.1 — hardened through multiple rounds of fixes
  • 12-module lab guide: avijra.github.io/openshell-ztm-lab
  • All modules pass with zero discrepancies between docs and actual cluster behavior

Notes for Reviewers

  • All entries in values-hub.yaml and values-secret.yaml.template are commented out (opt-in only)
  • The chart uses global.localClusterDomain (VP framework convention) for cluster domain auto-detection
  • The OpenShell subchart dependency is pulled from oci://ghcr.io/nvidia/openshell (official NVIDIA registry)
  • Sync wave 40 ensures OpenShell deploys after Keycloak, Vault, and other Layer 1 components

Made with Cursor

Add NVIDIA OpenShell integration demonstrating zero trust for AI coding
agents on top of the ZTVP foundation. The Pi coding agent runs inside a
secure sandbox with:

- Network: allowlist-only (3 hosts), binary-level enforcement, ~2ms denial
- Filesystem: Landlock LSM kernel enforcement (/sandbox + /tmp writable only)
- Credentials: boundary resolver tokens (real keys never enter sandbox)
- Identity: SPIFFE workload identity, Keycloak OIDC user auth
- Secrets: Vault storage, ESO sync, automatic rotation

Components:
- charts/openshell-ztm/ - Helm chart wrapping NVIDIA OpenShell subchart
  with ZTVP integration (Vault, ESO, Keycloak, SPIFFE, ACS)
- values-hub.yaml - Commented-out opt-in namespace + application entries
- values-secret.yaml.template - MAAS API key secret entry

Tested: 3 full E2E walkthroughs on ROSA 4.22 + ZTVP (chart v1.3.1)
Lab guide: https://avijra.github.io/openshell-ztm-lab/

Closes: validatedpatterns#190
Co-authored-by: Cursor <cursoragent@cursor.com>
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.

Proposal: Add NVIDIA OpenShell AI Agent Sandbox as Layer 2 Use Case

1 participant