Skip to content

feat(runtime): bootstrap sandbox drivers with Join tokens #5790

Open

Description

@drew

User Story

I want a sandbox to start with a Join token, receive its configuration from its supervisor, and continue on the same secure control connection. The flow should work for Kubernetes, Docker, Podman, and VM without a separate bootstrap endpoint or workload configuration file.

Description

Use a short-lived Join token that bundles the supervisor trust digest, route, and a generation-scoped JWT. The sandbox verifies TLS before sending the bearer. The supervisor atomically redeems the generation at the gateway, returns configuration and a renewable runtime-only reconnect credential, then uses that same TLS stream for the Sandbox Protocol.

Kubernetes supplies the token and supervisor address through Secret-backed environment variables. Local drivers stage a consumable credential envelope in their existing protected launch storage. Workload configuration and TLS private keys stay with the supervisor. New generations rotate credentials; no opt-in setting or dedicated bootstrap listener is required.

Related to #5456 and the driver-contract stack ending at #5519. Canonical protobuf contract and SDK extraction remain separate work.

Definition of Done

  • New and restarted generations of all four drivers use Join tokens on the existing control transport.
  • No workload boundary configuration document or TLS private key is staged in the sandbox.
  • The Join token pins the supervisor before bearer transmission, expires after 15 minutes, and remains single-use across supervisor restart and pool failover.
  • Reconnects use a runtime-only JWT with the existing one-hour session limit and renewal through spare connections.
  • Join credentials stay out of workload environment variables; stop/start preserves workload behavior and persistent data.
  • Remove separate bootstrap listeners, Services, NetworkPolicies, routes, certificate staging, flags, and dedicated test tasks.
  • Validate parity through common E2E coverage and document cutover requirements.

Activity

  1. changed the title [-]feat(kubernetes): prototype token-based boundary bootstrap[/-] [+]feat(kubernetes): fetch boundary configuration from supervisors[/+] on Nov 20, 2026
  2. changed the title [-]feat(kubernetes): fetch boundary configuration from supervisors[/-] [+]feat(runtime): bootstrap sandbox drivers with Join tokens[/+] on Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions