0.4.1
CubePod 0.4.1
Section titled “CubePod 0.4.1”Features and improvements
Section titled “Features and improvements”- Deterministic
volumeKeyworkspace persistence. PassvolumeKeywhen creating a sandbox to bind a deterministic/workspacePVC (PodBox.spec.volumeKey) that persists across sandbox delete and recreate cycles. Supported across the Gateway API, Kubernetes Controller, Python SDK, and TypeScript SDK. - Ordered egress policy rules. Configure ordered
allow/denyhost and wildcard rules vianetworkPolicy.egressonPodBoxandPOST /sandboxes, enforced consistently across the Gateway, Controller, and Zero-Trust Egress proxy. - Empty-body
archive-sync.POST /files/archive-syncinpodd, Gateway, and the Python SDK now accepts empty request bodies so callers can applyremove_pathscleanup without uploading a tar archive. - Bilingual documentation portal & Scalar API explorer. Added the English and Simplified Chinese Astro + Starlight documentation site at
cubepod.cubeplex.aiwith an interactive OpenAPI Explorer, auto-synced CRD and Helm Values references, andllms.txt/llms-full.txtbundles.
- CRD & policy action normalization. Added
volumeKeyandnetworkPolicy.egressfields to thePodBoxCRD schema and normalized egress rule actions in the Gateway and egress policy evaluator.
Before upgrading
Section titled “Before upgrading”Apply the updated Kubernetes CRDs before running helm upgrade, because Helm does not update files under crds/ on upgrade and PodBox adds spec.volumeKey and spec.networkPolicy.egress:
kubectl apply -f deploy/helm/cubepod/crds/Upgrade cubepod-controller, cubepod-gateway, cubepod-egress, and cubepod-podd together to v0.4.1 via the Kubernetes & Helm deployment guide, and update client SDKs (pip install -U cubepod / npm install cubepod@0.4.1).