Release Notes
Release notes describe user-visible enhancements, compatibility changes, and known limitations for Alauda Build of Agent Sandbox.
TOC
Supported Versionsv0.5.4-1Release InformationFeatures and EnhancementsBreaking and Behavioral ChangesSuspended condition contractImmutable volume claim templatesPython SDK connection optionKnown LimitationsSupported Versions
v0.5.4-1
Release Information
Features and Enhancements
- Improves warm-pool adoption, restart behavior, expectation tracking, and controller stability.
- Adds optimistic-lock and adoption-conflict handling for safer concurrent reconciliation.
- Restores SandboxTemplate hash label propagation to Pods so template-derived NetworkPolicies can select the intended workloads.
- Preserves explicit
falseand0values when Helm renders supported controller arguments. - Adds Kubernetes Event permissions required by the current controller behavior.
- Exposes declared container ports through the Sandbox Service.
- Includes controller lifecycle, cache, connection-sharding, webhook certificate, and efficiency improvements from upstream v0.5.4.
The ACP dynamic form remains intentionally limited to controller replicas, extension controllers, resources, node selector, and tolerations. Additional upstream flags are not exposed as overlapping ACP form controls in this release.
Breaking and Behavioral Changes
Suspended condition contract
Sandbox.status.conditions[type=Suspended] remains present after initial reconciliation. Clients must inspect the condition's boolean status instead of interpreting condition presence as suspended state.
The termination reason changes from PodNotTerminated to PodTerminating. Update scripts, dashboards, and alert rules that compare the old reason string.
Immutable volume claim templates
Sandbox.spec.volumeClaimTemplates is immutable after creation. Updates that add, remove, or modify a volume claim template are rejected. Create a replacement Sandbox when the template must change.
Python SDK connection option
The upstream Python SDK removes the use_pod_ip option. SDK consumers that still pass this option must update their code before adopting the corresponding SDK version.
Known Limitations
- Extension controllers are disabled by default. Enable
controller.extensionsbefore usingSandboxTemplate,SandboxWarmPool, orSandboxClaim. shutdownTimeis an absolute expiration time, not an idle timeout. Activity does not automatically extend it.- PersistentVolumeClaims preserve volume data but do not snapshot installed packages or operating-system changes in the container environment.
- The product does not provide an external HTTP API gateway for clients that should not use Kubernetes credentials.
- RuntimeClass implementations such as Kata Containers or gVisor must be installed and operated separately by the cluster administrator.
Internal packaging, scanning-governance registration, and uploader retry details are release-engineering evidence and are not product known issues.