Feature/secure access

[ninan-nn]

Background

Today, sandbox endpoints exposed through Kubernetes ingress gateway mode are reachable as long as the caller knows the public endpoint. We need an opt-in way to require an additional sandbox-scoped credential for endpoint access.

What changed

This PR adds secureAccess support for sandbox endpoint access.

Spec

• add optional secureAccess: boolean to CreateSandboxRequest
• document that secured endpoint responses include required access headers

Server

• validate runtime/exposure compatibility for secureAccess
• reject secureAccess=true for Docker runtime
• reject secureAccess=true unless Kubernetes ingress.mode='gateway'
• generate a secure access token during sandbox creation
• persist the token in workload annotations
• attach OPENSANDBOX-SECURE-ACCESS to endpoint response headers

Ingress

• extend sandbox endpoint resolution to include secure access metadata
• enforce OPENSANDBOX-SECURE-ACCESS on incoming requests
• return 401 when the header is missing or invalid
• strip the secure access header before forwarding HTTP traffic to backend

Kotlin SDK

• add secureAccess(...) support to sandbox builder and pool creation spec
• pass secureAccess through create sandbox requests
• ensure endpoint headers are propagated to execd/generated API requests
• redact the secure access header in HTTP logs

Tests

• add server unit tests for schema, Docker rejection, and Kubernetes token/header wiring
• add ingress tests for secure access enforcement
• add Kotlin SDK tests for request mapping and endpoint header propagation
• add Java E2E coverage for secured and unsecured endpoint access

Notes

• secureAccess is currently supported only for Kubernetes sandboxes exposed through ingress.mode='gateway'
• default behavior remains unchanged when secureAccess is omitted or false

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a19ee125c1

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[Pangjiping]

LGTM

[hittyt]

LGTM