Upgrade
Before you start, review the platform's Cluster Plugin upgrade process.
Before You Start
Confirm that the target web-cli package is published to the platform marketplace and that the selected version is compatible with your platform release. Review the target ModuleConfig before selecting a version.
Upgrade the Plugin
- Upload the new
web-clipackage through the platform's standard package publishing process. - Wait for the platform to synchronize the new version information before reviewing it in the Cluster Plugin list.
- Open the Cluster Plugins page, select the target cluster, and review the published version.
- Start the upgrade from the list or details page when the plugin's lifecycle supports standalone upgrades.
- If the platform marks the plugin as
Core, upgrade the cluster instead of performing a standalone plugin upgrade.
Verify the Upgrade
Run the following command in the global cluster:
Confirm that the status is Running and that TARGET_VERSION and CURRENT_VERSION both show the version you selected. NEW_VERSION reports the newest version available in the marketplace, so it can differ from the installed version without indicating a failure. Start a cluster terminal and run kubectl get nodes to verify end-to-end access.
Rollback Boundary
The platform controls the installed plugin version through ModuleInfo and the published ModuleConfig. When a rollback is required, select a previously published version through the platform upgrade workflow.