Docs

Volcengine Kubernetes Engine

Upgrade guide

Upgrading VCI Agent Sandbox

This topic describes how to upgrade an Agent Sandbox. Before upgrading, thoroughly review the target version's ‌changes and impact analysis to ensure a full understanding of the changes.

Preparations

You have confirmed Kubernetes compatibility, version changes, and impacts. For details, see Version change log.

You have administrator permissions for the cluster where the Agent Sandbox application is deployed. For details, see Configuring RBAC permissions.

As updates to some versions involve associated impacts, assess the scope of impact in advance and perform the upgrade during off-peak business hours.

If the current version is v0.1.1 and the warm pool feature is used, first scale in the number of warm pool replicas to 0 before the upgrade.

If you need to retain the ability to access the Sandbox via a Kubernetes Service, plan the value of the controller.defaultSandboxService parameter in advance.

Upgrade procedure

In the left navigation bar, click Application center > Helm.

On the Helm page, select the target cluster and namespace, and then find the Agent Sandbox application to upgrade.

On the right side of the Agent Sandbox application, click ...> Update in the Actions column.

On the Update Helm page, expand agent-sandbox from the Application template drop-down list in the Orchestration template section, and then select the target version.

Click the edit icon next to values.yaml and fill in the deployment parameters. For parameter details, see the installation guide.

After confirming the parameters are correct, click Confirm at the bottom of the page to submit the update.

VKE will automatically complete the rolling upgrade of the Helm Release. You can observe the release status and workload changes on the Helm details page.

Post-upgrade verification

After the upgrade is complete, we recommend performing checks in the following order to ensure that the application is running normally.

On the Helm page, confirm that the agent-sandbox application status is Deployed and its Chart version matches the target version.

Click the Helm application name. On the Helm details page, check the workload type and status of agent-sandbox-controller. The expected results are that the type has switched to Deployment, and that all its Pods are in the Running status.

tip

The agent-sandbox-controller workload type is ‌Deployment‌ ‌in v0.4.6 or later‌, and StatefulSet before this version.

The status of all agent-sandbox-controller resources must be ready (the Status column shows Ready: n/n).

Create a test Sandbox to verify that it can normally reach the Running state and be accessed. For detailed instructions, see Lifecycle management.

(Optional) If anomalies occur after the upgrade, roll back to the previous stable version on the Helm page using the Historical version feature. Rollback will also result in a brief window during which the add-on is unavailable. Proceed with caution.

Last updated: 2026.07.24 18:38:16