v0.6.0 #1146
fslongjin
announced in
Announcements
v0.6.0
#1146
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
2026.07.24 Release v0.6.0
CubeSandbox 0.6.0 continues to strengthen core capabilities for production deployment and operations.
This release introduces 6 major features along with multiple enhancements and bug fixes. 92 commits from 31 contributors.
🎯 Major Features
Kubernetes Deployment: Deploy Cube Control Plane and Compute Nodes on K8s
Deploy CubeSandbox control-plane components and compute nodes directly onto Tencent Cloud TKE, standard Kubernetes, or k3s clusters via Helm Chart. Perform rolling upgrades, canary releases, and other operations using standard Kubernetes practices. For details, see the Kubernetes Deployment Guide.
::: warning Preview
Kubernetes deployment is currently in preview. Advanced capabilities such as seamless upgrades are still under active development. Feedback is welcome.
:::
E2B-Compatible Volume Framework
Introduces an E2B-compatible Volume framework that lets users plug in custom backend storage while remaining compatible with the E2B standard. Provides four hooks — Create / Destroy / Attach / Detach — and two plugin forms: Binary and RPC. This release includes Volume lifecycle management, sandbox–Volume binding APIs, and supporting SDK and cubemastercli capabilities. For details, see the Volume Plugin Guide.
Template Aliases
Support setting an alias when creating a template, and creating sandboxes by specifying that alias.
Note: Aliases can only be set at template creation time; existing templates cannot have aliases added or changed. Specifying an alias when creating a sandbox is currently supported only in the Python SDK; other SDKs will follow soon.
Configurable Host for Inbound Sandbox Requests
Allow configuring the
Hostheader forwarded to the sandbox (instead of the default<port>-<sandboxId>.<domain>), improving compatibility with Host-based services inside the sandbox. The newnetwork.maskRequestHostparameter can be set when creating a sandbox to specify theHostforwarded to in-sandbox services (for examplelocalhost:${PORT}, which expands tolocalhost:3000when accessing port 3000), so applications that rely on Host for routing, validation, or callbacks work correctly.Compute Node Isolation
Support isolating a compute node at the scheduling layer so operators can log in for maintenance, upgrades, and troubleshooting. After isolation, no new sandboxes are scheduled to that node; existing sandboxes continue to run unaffected.
Isolate a node with
cubemastercli node isolate <node-id>, and lift isolation with theunisolatesubcommand. For details, see Node Isolation.CubeOps Operations Service: Decouple Ops & Web Console Logic from CubeAPI
Web console capabilities are split out of the CubeAPI module into a standalone CubeOps service, making CubeAPI lighter and more extensible.
✨ Enhancements
SDK
Templates & Storage
tpl info/delete/redo.Lifecycle & Control Plane
CUBE_AUTO_MIGRATIONenv var to skip automatic DB migration at startup for controlled upgrades.Networking & Security Proxy
Deployment & Runtime
Web UI / CubeOps / Other
🐛 Bug Fixes
Lifecycle & Sandbox
Security & Validation
📚 Documentation
This discussion was created from the release v0.6.0.
All reactions