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.
This topic describes only the components that support the end-to-end canary release feature. If you need to know information about the components that support other features, , and contact Alibaba Cloud technical personnel.
End-to-end canary release
In addition to the components listed in this topic, if other components need to support the end-to-end canary release feature, , and contact Alibaba Cloud technical personnel.
|Component||Supported version||End-to-end canary release|
|Machine tagging||Traffic tagging||Machine pass-through tagging|
|Dubbo||2.5.3 to 2.6.x|
|3.0.5 and later|
Note Nacos, Eureka, and ZooKeeper instances support machine tagging.
|HttpClient + K8s Service||OKHttp|
|Gateways||Spring Cloud Gateway|
|Spring Cloud Zuul|
Note You cannot configure rules for traffic tagging and machine pass-through tagging in the MSE console. You must 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 Ingress gateways.
You can use the official version of MSE agents to enable Microservices Governance for the applications that use JDK 1.6, JDK 1.7, or JDK 1.8. The applications that use JDK 11 or JDK 17 are being tested by using canary releases to determine whether Microservices Governance can be enabled for the applications. If you want to enable Microservice Governance for the applications that use JDK 11 or JDK 17, , and contact Alibaba Cloud technical personnel.