mirror of https://github.com/NVIDIA/OpenShell.git synced 2026-11-07 08:55:37 +08:00

Files

T

Taylor Mutch d1a797acbd feat(kubernetes): add sidecar supervisor topology

Add the Kubernetes sidecar supervisor topology, its Helm/Skaffold configuration, topology documentation, and sidecar e2e matrix coverage. Skip root-only sandbox identity rewriting when process enforcement is network-only so the low-permission sidecar process container can start successfully.

Signed-off-by: Taylor Mutch <taylormutch@gmail.com>

2026-07-06 21:01:09 -07:00

src

feat(kubernetes): add sidecar supervisor topology

2026-07-06 21:01:09 -07:00

build.rs

feat(providers): support SPIFFE-backed token grants (#1784 )

2026-06-10 10:54:39 -07:00

Cargo.toml

test(e2e): stop using custom e2e binary builds (#2000 )

2026-06-25 13:08:04 +00:00

README.md

docs(architecture): reset subsystem docs (#1184 )

2026-05-07 08:59:02 -07:00

README.md

openshell-core

Shared types, constants, configuration, and helpers used across OpenShell crates.

Object Metadata

Top-level user-facing objects use a Kubernetes-style metadata convention. The metadata shape provides:

Stable server-generated ID.
Human-readable name.
Creation timestamp.
Optional labels for filtering and automation.

Code that works with object metadata should use the traits in openshell_core::metadata instead of reaching into protobuf fields directly:

use openshell_core::{ObjectId, ObjectLabels, ObjectName};

let id = sandbox.object_id();
let name = sandbox.object_name();
let labels = sandbox.object_labels();

Trait methods must tolerate missing metadata and return safe empty values rather than panicking.

Label Rules

Labels follow Kubernetes-style key and value conventions:

Keys may include an optional DNS-prefix followed by /.
Names are limited to alphanumeric characters plus -, _, and ..
Values use the same character set and may be empty.
Selectors use comma-separated key=value pairs with AND semantics.

Validate labels at API ingress before persisting objects.

Inference Profiles

Provider inference profiles live in this crate so the gateway, sandbox, and router agree on provider defaults. Profiles define:

Auth header style.
Default upstream headers.
Client-supplied passthrough headers.
Supported inference protocol shapes.

Do not duplicate provider-specific inference behavior in callers. Add shared behavior here, then consume it from the gateway, sandbox, and router.