Istio Gray Release
Istio provides you with microservice-based traffic governance capabilities. Istio allows you to develop a set of traffic distribution policies based on standards and deliver the policies to application pods in a non-intrusive manner, implementing smooth and stable grayscale 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 Configuration Diagnosis Result of the corresponding service on the Service Management tab page is in the normal state. If the ASM service is not enabled, enable the ASM service.
- An Istio workload has been created and associated with the Service of the current version.
Procedure
Parameter |
Description |
---|---|
Action Name |
Name of an added deployment action. Max 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. |
Release Mode |
Custom and Fast are supported. |
File Source |
|
Control Options |
Continue the task even if this action fails. |
Parameter |
Description |
---|---|
Action Name |
Name of an added deployment action. Max 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. |
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. Gray release policy:
|
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. |
|
Control Options |
Continue the task even if this action fails. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot