Upgrading a Microservice Engine Version

Microservice engines are created using the latest engine version. When a later version is released, you can upgrade your engine.

During the microservice engine upgrade, the microservice and engine are intermittently disconnected, but services of running microservices are not affected. You are advised not to upgrade, restart, or change microservices when upgrading a microservice engine.
Only exclusive microservice engines can be upgraded. Version rollback is not supported after the upgrade.
For details about the precautions for upgrading an exclusive microservice engine from 1.x to 2.x, see What Do I Need to Know Before Upgrading an Exclusive Microservice Engine?

Background

During upgrade, two instances are upgraded in rolling mode without service interruptions. However, one of the two access addresses may be unavailable. In this case, you need to quickly switch to the other instance. Currently, ServiceComb SDK and Mesher support instance switching. If you call the APIs of the service center and configuration center for service registry and discovery, instance switching is required.

Procedure

Log in to ServiceStage and choose Cloud Service Engine > Engines.
Select the target microservice engine from the Microservice Engine drop-down list in the upper part of the page.
In the Microservice Engine Information area, click Upgrade.

Select Target Version and view the version description. Determine whether to upgrade the software to this version.
Click OK.
If the upgrade fails, click Retry to perform the upgrade again.