New versions are released continuously during application iterations. Before you release a new version, you can use traffic adjustment rules to verify the new version on a small number of instances. After the verification succeeds, you can upgrade the applications on all instances to the new version. You can use HSF and HTTP traffic adjustment rules. This topic describes these two rules.
Prerequisites
- A group is created. For more information, see Create a group.
- If you use a RAM user to perform end-to-end traffic adjustment, the RAM user is granted the permissions to view clusters, applications, and services, and manage applications and services. For more information, see Replace EDAS-defined permissions with RAM policies.
Configure an HTTP traffic adjustment rule
You can specify the URL and use the Cookie value, Header value, or URL parameter to distribute the traffic based on the whitelist or the range of the remainder of Mod 100.
Configure an HSF traffic adjustment rule
You can specify a service or a method, use the parameter value of the method, and use the remainder range of Mod 100 or the list as the condition to distribute the traffic.
Verify the traffic adjustment rule
After you configure and enable a traffic adjustment rule, you can monitor the canary traffic to verify whether the traffic destined for the canary instance group meets your expectations. For more information, see Monitor canary traffic.