If you want to update a multilingual microservice-oriented application that is deployed in a Kubernetes cluster, you can use canary releases. You can update the application and verify the new version on a small number of instances. After the verification succeeds, you can update the application on all instances to the new version. This ensures service stability and performance during the update.


  1. Log on to the EDAS console.
  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region.
  3. On the Applications page, select a microservice namespace. Then, select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list, and click the name of the application that you want to release.
  4. In the upper-right corner of the Application Overview page, choose Deploy > Deploy.
  5. On the Select Deployment Mode page, click Start Deployment in the upper-right corner of the Canary Release (Phased) section.
  6. On the page that appears, set the parameters in the Service Mesh and Release Policy sections, and configure canary release rules. Then, click OK.
    1. Set the parameters in the Service Mesh section.
      Table 1. Parameters in the Service Mesh section
      Parameter Description
      Protocol The protocol that is used by the service. Valid values: http, http2, gRPC, and TCP.
      Service Name The name of the service that is provided by the application.
      Service Port The port number of the service that is provided by the application.
      Note The values of the Service Name and Service Port parameters must be the same as those in the application code. Otherwise, the service cannot be registered or called.
    2. Set the parameters in the Release Policy section.
      Table 2. Parameters in the Release Policy section
      Parameter Description
      Number of Instances for Canary Release The number of application instances for the release in the first phase. You can view the total number of instances on the right side of this parameter. To ensure application stability, we recommend that you set this parameter to a value less than half of the total number of instances.
      Remaining Batches The number of remaining phases to release the application. After the application is released in the first phase, the application is released on the remaining instances based on the value of this parameter.
      Note The Batch Mode parameter is displayed only when the number of remaining phases is greater than 1.
      Deployment Interval Between Batches If the number of application instances in each phase is greater than 1, the application is deployed to the application instances at the specified interval. Unit: seconds.

      The Publish Policy Configuration section on the right side shows the procedure for the canary release based on the configuration.

    3. Configure canary release rules.

      EDAS supports the following canary release rules: Canary Release by Content and Canary Release by Ratio.

      Table 3. Parameters for canary release rules
      Tab Parameter Description
      Canary Release by Content Protocol Type The value is fixed to Service Mesh.
      Path The path in the HTTP requests for the canary multilingual application.
      Conditions You can set this parameter based on the HTTP header value.
      Canary Release by Ratio Traffic Ratio The proportion based on which the traffic is distributed to the canary application.
      Note You can click Create Inbound Traffic Rule to create multiple inbound traffic adjustment rules. The rules can take effect at the same time.
    4. Optional:Configure advanced settings.

    After a canary release is started, EDAS deploys the new version of the application to the specified canary instance group. The deployment progress and status are displayed on the Upgrade History page.

    Note You can monitor the canary traffic to check whether the traffic is distributed to the canary group as expected. For more information, see Monitor canary traffic.
  7. After the traffic for the canary release is verified, click Start the Next Batch on the right side of the Upgrade History page. Complete the release of the subsequent phases.
    If issues occur during the verification, you can click Undo in the upper-right corner of the Upgrade History page. In the Undo the Verification message, click OK.

Verify the result

After the canary release is complete, check whether the deployment package is of the new version on the Application Overview page.