This topic describes the component support for the end-to-end canary release feature of Microservices Engine (MSE) Microservices Governance. This helps you evaluate your microservices governance solution.
Usage notes
This topic describes only the components that support the end-to-end canary release feature of MSE. For more information about components that support other features of MSE, join the DingTalk group (ID: 34754806) to contact technical support.
Supported components
If you require components that are not included in this topic when you use the end-to-end canary release feature of MSE, join the DingTalk group (ID: 34754806) to contact technical support.
Component | Supported version | End-to-end canary release | ||
Machine tagging | Traffic tagging | Machine pass-through tagging | ||
Dubbo | 2.5.3~2.6.x |  | | |
2.7.x | | | | |
3.0.5 and later | | | | |
Spring Cloud |
| Note Nacos, Eureka, and ZooKeeper instances support machine tagging. | | |
2020 | | | ||
2021 | | | ||
HttpClient + K8s Service | OKHttp |  | | |
ApacheHttp | | | | |
JDK Http | | | | |
Gateways | Spring Cloud Gateway | | | |
Spring Cloud Zuul | | | | |
Ingress gateways | | Note You cannot configure rules for traffic tagging and machine pass-through tagging in the MSE console. You need to manually configure the tagging rules in the Container Service for Kubernetes (ACK) console. For more information, see Configure an end-to-end canary release based on MSE Ingress gateways. | ||
Cloud-native gateways | | | | |
Supported JVM components
The applications that use JDK 1.6, JDK 1.7, JDK 1.8, JDK 11, or JDK 17 support the end-to-end canary release feature when an official version of MSE agents is used.