Docs

Volcengine Kubernetes Engine

FSX client

Migrating FSX clients

FSX client migration implements lifecycle management for FSX clients based on the FSXSet CRD. It supports features such as rolling upgrades, canary upgrades, and multi‑environment isolation. This topic describes the migration procedure, verification method, and subsequent cleanup operations for FSX clients.

tip

Before performing the migration, you need to first familiarize yourself with the migration background and the changes to the csi-fsx add-on. For more information, see [Product update] fsx-service deprecation notice.

Migration steps

tip

To migrate FSX clients, you need to first install the fsxset-controller add-on and then upgrade the csi-fsx add-on to v1.0.0 or later.

Step 1: Install the fsxset-controller add-on

In the left navigation bar, click Cluster. In the right part of the page, click the target cluster name to go to its management page.

In the left navigation pane, select Addons and click the Storage tab.

Move the pointer over the fsxset-controller add-on card and click Deploy to install the add-on.

Step 2: Upgrade the csi-fsx add-on

In the left navigation pane, select Addons and click the Storage tab.

In the upper-right corner of the csi-fsx add-on card, click ... > Upgrade.

In the pop-up dialog box, click Confirm to upgrade the add-on.

After the upgrade is complete, view the add-on version to confirm that the add-on has been upgraded to v1.0.0 or later.

Validate results

Migrate existing configurations

If you enable the multi-client configuration feature for the original fsx-service add-on, when the csi-fsx add-on is upgraded to v1.0.0 or later, the system will automatically perform the following operations to ensure a smooth transition of configurations.

The system automatically creates a default FSXSet configuration named default.

The specified FSX client parameters (such as client resource quotas) will be automatically migrated to the FSXSet configuration named default. You can view the corresponding resources through the console or kubectl to confirm that the configurations have been automatically migrated.

Nodes without labels will be automatically assigned to the default group and use the default configuration.

Take over existing FSX clients

After you upgrade the csi-fsx add-on to v1.0.0 and enable FSXSet management, the system will automatically take over the existing FSX client Pods created by the fsx-service add-on of the earlier version. This ensures that existing FSX clients run as expected. This operation is automatically completed by the system and requires no manual intervention.

View FSXSet resources

After upgrading csi-fsx to v1.0.0, you can view the system‑generated FSXSet resources by using the following methods:

View resources via the console

View resources via kubectl

In the left navigation bar, click Cluster. Click the target cluster name to go to the management page of this cluster.

In the left navigation pane, select Addons and click the Storage tab.

In the lower-right corner of the csi-fsx add-on card, click ... > Client configuration.

In the Client configuration panel, view the FSXSet resources in the system.

Find the target resource and click Update in the Actions column to view or update the FSXSet resource.

tip

To configure more features, you can view or modify the YAML configurations of the FSXSet resources by navigating to Workload > Resource Explorer.

Subsequent configurations

Clean up the fsx-service add-on

After you upgrade csi-fsx to v1.0.0, it has fully taken over all features of the original fsx-service. Therefore, after confirming that the migration is complete, you can uninstall the fsx-service add-on to save cluster resources. For instructions on removing the add-on, see Uninstalling add-ons.

Last updated: 2026.07.24 10:53:35