Upgrade an MSE cloud-native gateway-Microservices Engine(MSE)-阿里云帮助中心

You can upgrade the version and edition of a Microservices Engine (MSE) cloud-native gateway.

Important

Gateway upgrades do not affect short-lived connections. However, persistent connections such as WebSocket or gRPC connections may be briefly disconnected. If your gateway relies heavily on persistent connections, we recommend that you perform the upgrade during off-peak hours.
For standalone instances earlier than V1.2.11, short-lived connections are disconnected during the upgrade. For V1.2.11 and later, short-lived connections are not affected.

Prerequisites

Log on to the MSE console. In the top navigation bar, select a region.
In the left-side navigation pane, choose Cloud-native Gateway > Gateways.
On the Gateways page, find the gateway to upgrade and click Manual Upgrade in the Version column. In the Gateway Version Upgrade dialog box, click OK.

The upgrade takes about 5 to 10 minutes.

Log on to the MSE console. In the top navigation bar, select a region.
In the left-side navigation pane, choose Cloud-native Gateway > Gateways.
On the Gateways page, find the gateway to upgrade and choose More > Upgrade/Downgrade in the Actions column.
On the Upgrade/Downgrade page, select Professional Edition for Product Edition, and ensure that the Number of Nodes is at least 2.

Important
For regions that support Gzip hardware acceleration, the system enables Gzip Hardware Acceleration by default. To use this feature, make sure that Instance Type is set to 8 cores, 16 GB or higher. Otherwise, clear Gzip Hardware Acceleration.
Click Purchase to complete the upgrade.

If the Purchase button is grayed out, follow the on-screen instructions to resolve the issues, and then click the button. The upgrade takes about 4 to 5 minutes.

When you upgrade or restart an MSE cloud-native gateway, the underlying nodes are rebuilt and their internal IP addresses may change.
If your Elastic Compute Service (ECS) security group rules allow only fixed node IP addresses, the new IP addresses may not be covered after the upgrade or restart, which causes access interruptions.
We recommend that you allow the CIDR block of the vSwitch in your Virtual Private Cloud (VPC) in your ECS security group rules instead of individual node IP addresses. Before the upgrade, check how your ECS security group rules are configured. If fixed IP addresses are used, change them to CIDR-block-based rules in advance.