Istio Gray Release

Prerequisites

• A CCE cluster is available. If no CCE cluster is available, create one.
• A workload of the current version exists and a service has been created. If no workload exists, create a workload.
• The ASM service has been enabled and the created service is normal. To check the service status, go to the Service Management page and check its Configuration Diagnosis Result.
• An Istio workload has been created and associated with the Service of the current version.

Configuring Deployment Actions

1. Create an application by referring to Creating an Application.
2. On the Deployment Actions page, add this deployment action based on the service scenario.
3. Configure the action using the parameters described in the table below.

   Table 1 Parameters of custom release mode

   Parameter	Description
   Action Name	Custom action name. Enter 1 to 128 characters. Do not start or end with a space. Use letters, digits, spaces, and these special characters: -_,;:./()
   Cluster Name	Select a target cluster.
   Namespace	Enter a namespace name.
   Release Mode	Custom and Fast are supported.
   File Source	Artifact YML File: Select the target YML file. Repo Repo: Select the target code repository. Branch: Select the target branch. YML File Path: path of the target YML file.
   Action Control	Continue the task even if this action fails.

   Table 2 Parameters of fast release mode

   Parameter	Description
   Action Name	Custom action name. Enter 1 to 128 characters. Do not start or end with a space. Use letters, digits, spaces, and these special characters: -_,;:./()
   Cluster Name	Select a target cluster.
   Namespace	Enter a namespace name.
   Release Mode	Custom and Fast are supported.
   Traffic Takeover	Gray release VirtualService Name: Select the target VirtualService. Log in to the ASM console, choose Mesh Configuration > Istio Resource Management and filter the target namespace and istio resources. DestinationRule Name: Select the target destination rule. Log in to the ASM console, choose Mesh Configuration > Istio Resource Management and filter the target namespace and istio resources. Current Version: Use the keyword "version" in the label to distinguish the official version from the gray version. The version number must be the same as the subsets object name in DestinationRule and is used as an identifier for gray traffic distribution. Gray Version Number: Use the keyword "version" in the label to distinguish the official version from the gray version. The version number must be the same as the subsets object name in DestinationRule and is used as an identifier for gray traffic distribution. Grayscale release policy: Based on traffic ratio Gray Version Traffic (%): Traffic can be customized. Based on request content-Cookie Cookie Content: Custom cookie content can be entered. Based on request content-Header Custom Header: Headers can be added and customized.
   	Official release VirtualService Name: Select the target VirtualService. Log in to the ASM console, choose Mesh Configuration > Istio Resource Management and filter the target namespace and istio resources. DestinationRule Name: Select the target destination rule. Log in to the ASM console, choose Mesh Configuration > Istio Resource Management and filter the target namespace and istio resources. Official Version: Enter the version that officially takes over traffic.
   Action Control	Continue the task even if this action fails.

Helpful Links

If you encounter any problem during deployment, see Grayscale Release with Istio.