All Products
Search

This Product

    Microservices Engine:Upgrade an MSE cloud-native gateway

    Document Center

    Microservices Engine:Upgrade an MSE cloud-native gateway

    Last Updated:Aug 10, 2026

    You can upgrade the version 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

    Create a cloud-native gateway

    Version upgrade

    1. Log on to the MSE console. In the top navigation bar, select a region.

    2. In the left-side navigation pane, choose Cloud-native Gateway > Gateways.

    3. 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.

    Notice

    • 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.