Alauda Build of Agent Sandbox Docs
  • English

    • Lifecycle Policy

    Alauda Build of Agent Sandbox is an independently installable Cluster Plugin. Its release cycle and version number are separate from the ACP core release cycle.

    TOC

    Independent Release CycleSupported Version CombinationUpgrade PolicyRollback BoundaryTech Preview Support Scope

    Independent Release Cycle

    An ACP release stream can support an Agent Sandbox version without using the same version number. Always identify both versions when planning installation or upgrade:

    • ACP release stream identifies the platform compatibility target.
    • Product and ModulePlugin version identifies the installable Agent Sandbox package.
    • Helm Chart version identifies the packaged chart metadata.
    • Upstream version identifies the Kubernetes SIGs source baseline.

    Supported Version Combination

    The following combination has been validated for this Tech Preview:

    Agent SandboxHelm ChartACPUpstreamStatus
    v0.5.4-10.5.4-1v4.4v0.5.4Tech Preview, validated

    The package is available for the ACP v4.4 release stream in the Application Center. This page does not extend compatibility to other ACP release streams that have not been validated.

    Upgrade Policy

    The upgrade risk level is High because upstream v0.5.4 changes observable API and status behavior. Before upgrading:

    1. Review the breaking and behavioral changes in Release Notes.
    2. Inventory automation that reads Sandbox conditions or edits volume claim templates.
    3. Save important custom resource manifests.
    4. Confirm that persistent data has an application-appropriate backup or recovery path.
    5. Verify the controller and existing Sandboxes after the upgrade.

    Use Upgrade to change the plugin version. Use Update only to change the configuration of the currently installed version.

    Rollback Boundary

    This release does not promise a lossless downgrade. Rolling back the controller cannot automatically restore old client assumptions about condition presence or reason strings. It also cannot make an invalid in-place update to spec.volumeClaimTemplates valid.

    If a workload definition must change an immutable volume claim template, create a replacement Sandbox and migrate data through an application-controlled process.

    Tech Preview Support Scope

    This documentation records the version combination and behaviors that were validated for ACP v4.4. It does not define an unapproved end-of-life date, maintenance window, or production service-level agreement. Apply the ACP Tech Preview policy and your organization's change-management requirements when evaluating production use.