For the complete documentation index, see llms.txt. This page is also available as Markdown.

Kubernetes

Kubernetes provider for ComputeSDK — run each sandbox as a Pod in your cluster and execute commands via pods/exec.

Installation

npm install @computesdk/k8s

Setup

The provider uses your current kubeconfig context by default. It calls loadFromDefault() from @kubernetes/client-node, which reads $KUBECONFIG if set, otherwise ~/.kube/config. Override with kubeConfigPath or context in the provider config if you need to target a specific cluster.

The identity used by your kubeconfig needs the following RBAC in the target namespace:

Resource
Verbs

pods

create, get, list, delete

pods/exec

create

services

delete

services: delete is required because destroy opportunistically cleans up a Service named <pod-name>-svc (in case one was created out-of-band to back getUrl). The provider never creates Services itself.

Local clusters (kind, k3d, minikube, Docker Desktop) grant cluster-admin by default and need no extra setup.

Usage

import { k8s } from '@computesdk/k8s';

const compute = k8s({
  namespace: 'default',
  runtime: 'node',
});

// Create sandbox
const sandbox = await compute.sandbox.create();

// Run a command
const result = await sandbox.runCommand('echo "Hello from k8s!"');
console.log(result.stdout); // "Hello from k8s!"

// Clean up
await sandbox.destroy();

Sandbox IDs are namespace-prefixed: <namespace>/<podName> (e.g. default/computesdk-sbx-abc12345). create(), getById(), and list() all return this form, so values round-trip without normalization. getById() and destroy() also accept a bare Pod name for convenience — bare IDs are resolved against the provider's configured namespace.

Pod Layout

Each sandbox is a single Pod with one container:

  • Pod name: <podNamePrefix>-<up to 8 random base36 chars> (default prefix computesdk-sbx).

  • Container name: sandbox — use this with kubectl exec (e.g. kubectl exec -it -c sandbox <pod> -- /bin/sh).

  • Labels: computesdk.io/managed=true, computesdk.io/runtime=<node|python>, computesdk.io/sandbox-id=<pod-name>.

  • Annotations: any metadata you pass to create() is stored as computesdk.io/meta-<key>. Non-string values are JSON-stringified.

  • Restart policy: Never. Pods are one-shot; recreate the sandbox if the container dies.

compute.sandbox.list() returns Pods in the configured namespace that match computesdk.io/managed=true. Sandboxes in other namespaces are not returned.

Run Commands

Background commands are launched with nohup and their combined stdout/stderr is redirected to /tmp/computesdk-bg.log inside the Pod. Tail it with another runCommand('cat /tmp/computesdk-bg.log') if you need the output.

Environment Variables

Pass environment variables to the Pod at creation time:

These are set on the Pod's container spec and available to every command in the sandbox.

Port Forwarding

getUrl is template-based in this MVP — set urlTemplate to construct routable URLs through your own ingress, gateway, or DNS pattern. The provider substitutes these placeholders:

Placeholder
Value

{protocol}

From the protocol option (default http)

{service}

<pod-name>-svc

{namespace}

Pod namespace

{port}

From the port option

If urlTemplate is not set, getUrl returns a placeholder URL ending in .invalid so misconfiguration is obvious.

Configuration Options

Kubeconfig loading precedence:

  1. kubeConfigRaw

  2. KUBECONFIG_B64 (base64-encoded kubeconfig)

  3. kubeConfigPath

  4. default kubeconfig resolution

Limitations

  • Filesystem methods are not implemented in this MVP — use runCommand with cat, tee, etc. to read and write files.

  • The provider never creates Kubernetes Services. getUrl is purely template-based — set urlTemplate to match your existing routing setup (ingress, gateway, or DNS).

  • Pod resource requests and limits are fixed (250m / 256Mi requests, 1 CPU / 1Gi limits). Set image if you need a different runtime; CPU/memory are not yet configurable.

  • Pods use restartPolicy: Never. If the container exits, the sandbox is gone — create a new one.

  • compute.sandbox.list() only scans the namespace configured on the provider; it does not enumerate across namespaces.

Last updated

Was this helpful?