- What's New
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Application Service Mesh
- Buying a Service Mesh
- Mesh Management
- Service Management
- Gateway Management
- Grayscale Release
- Mesh Configuration
- Traffic Management
- Security
-
Best Practices
- Upgrading Data Plane Sidecars Without Service Interruption
- Service Governance for Dubbo-based Applications
- Reserving Source IP Address for Gateway Access
- Creating a Service Mesh with IPv4/IPv6 Dual Stack Enabled
- How Do I Query Application Metrics in AOM?
- Reducing the Agency Permissions of ASM Users
- Istio-ingressgateway HA Configuration
-
FAQs
- Service Mesh Cluster
-
Mesh Management
- Why Cannot I Create a Mesh for My Cluster?
- Why Are Exclusive Nodes Still Exist After Istio Is Uninstalled?
- How Do I Upgrade ICAgent?
- How Do I Enable Namespace Injection for a Cluster?
- How Do I Disable Sidecar Injection for Workloads?
- What Can I Do If A Pod Cannot Be Started Due to Unready Sidecar
- How Do I Handle a Canary Upgrade Failure?
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- How Do I Inject a Sidecar for the Pod Created Using a Job or CronJob?
- Performing Grayscale Release
-
Managing Traffic
- Why Are the Created Clusters, Namespaces, and Applications Not Displayed on the Traffic Management Page?
- How Do I Change the Resource Requests of the istio-proxy Container?
- Does ASM Support HTTP/1.0?
- How Can I Block Access from Some IP Address Ranges or Ports for a Service Mesh?
- How Do I Configure max_concurrent_streams for a Gateway?
- How Do I Fix Compatibility Issues Between Istio CNI and Init Containers?
-
Monitoring Traffic
- Why Cannot I View Traffic Monitoring Data Immediately After a Pod Is Started?
- Why Are the Latency Statistics on the Dashboard Page Inaccurate?
- Why Is the Traffic Ratio Inconsistent with That in the Traffic Monitoring Chart?
- Why Can't I Find Certain Error Requests in Tracing?
- Why Cannot I Find My Service in the Traffic Monitoring Topology?
- How Do I Connect a Service Mesh to Jaeger or Zipkin for Viewing Traces?
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- User Guide
-
FAQs
- Service Mesh Cluster
- Mesh Management
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- Performing Grayscale Release
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Basic Operations on a Grayscale Task
Description
Basic operations on a grayscale version are performed by modifying the configuration of the DestinationRule and VirtualService resources of Istio. After the modification is complete, wait for about 10 seconds for the new policy to take effect.
Modifying the Traffic Policy of a Grayscale Version
Modifying a grayscale policy that is based on traffic ratio
For such a grayscale policy that is based on traffic ratio, you can gradually increase the traffic ratio of the grayscale version to avoid service risks caused by direct traffic switchover. To change the traffic ratio, perform the following steps:
- Log in to the ASM console and click the name of the target service mesh to go to its details page.
- In the navigation pane, choose Grayscale Release. Then click the target canary release task.
- On the Configure Traffic Policy page, set the traffic ratio of the grayscale version.
If the traffic ratio of the grayscale version is set to x, the traffic ratio of the original version is automatically adjusted to 100-x.
- Click Deliver Policy.
Modifying a grayscale policy that is based on request content
With such a policy, a grayscale version can be accessed only when the traffic meets the rules based on Cookies, Headers, Queries, Allowed Operating Systems, and Allowed Browsers. In real-world use cases, rules may be modified for multiple times to fully verify the performance of the grayscale version.
- Log in to the ASM console and click the name of the target service mesh to go to its details page.
- In the navigation pane on the left, choose Grayscale Release and click the target canary release task.
- On the Configure Traffic Policy page, reconfigure Cookie, Header, Query, Allowed OS, and Allowed Browser.
- Click Deliver Policy.
Switching the Grayscale Policy Type
You can change the type of a grayscale policy from based on request content to based on traffic ratio and vice versa. After this operation is complete, all configured rules become invalid and all traffic is redistributed based on the new policy.
Grayscale policies can be changed only for running tasks. After a grayscale version is released (that is, the new version completely takes over the traffic and the old version has been brought offline), its grayscale policy cannot be reconfigured.
- Log in to the ASM console and click the name of the target service mesh to go to its details page.
- In the navigation pane on the left, choose Grayscale Release and click the target canary release task.
- On the Configure Traffic Policy page, change the policy type.
- Click Deliver Policy.
Taking Over All Traffic
After you click Take Over All Traffic, the original version or grayscale version takes over all traffic.
- Log in to the ASM console and click the name of the target service mesh to go to its details page.
- In the navigation pane on the left, choose Grayscale Release and click the target grayscale release task.
- On the Monitor and Manage Traffic page, click Take Over All Traffic next to the target version.
Figure 1 Taking over all traffic
- In the displayed dialog box, click OK.
Terminating a Grayscale Release Task
After the grayscale version takes over all traffic, you can terminate the grayscale task. After the grayscale task is canceled, the original version will be brought offline, and all workloads and Istio configuration resources will be deleted.
- Log in to the ASM console and click the name of the target service mesh to go to its details page.
- In the navigation pane on the left, choose Grayscale Release and click the target grayscale release task.
- On the Monitor and Manage Traffic page, click Take Over All Traffic next to the grayscale version.
- Click Terminate Task in the lower right corner.
- In the displayed dialog box, click OK.
You can go to the Terminated Tasks tab page to view the finished grayscale task. The Release Result is Released successfully.
Canceling a Grayscale Release Task
After the original version takes over all traffic, you can cancel the grayscale task.
- Log in to the ASM console and click the name of the target service mesh to go to its details page.
- In the navigation pane on the left, choose Grayscale Release and click the target grayscale release task.
- On the Monitor and Manage Traffic page, click Take Over All Traffic next to the original version.
- Click Cancel Task in the lower right corner. You can also click
in the upper right corner of a task in the grayscale task list.
- In the displayed dialog box, click OK.
You can go to the Terminated Tasks tab page to view the finished grayscale task. The Release Result is Released canceled.
Viewing Terminated Grayscale Release Tasks
You can view canceled and finished grayscale tasks on the Terminated Tasks tab page.
- Log in to the ASM console and click the name of the target service mesh to go to its details page.
- In the navigation pane on the left, choose Grayscale Release and click the Terminated Tasks tab page.
You can view the release task name, release result, service, and release time, and delete a terminated task.
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