All Products
Search
Document Center

Microservices Engine:End-to-end canary release

Last Updated:Jan 10, 2025

Microservices Governance of Microservices Engine (MSE) provides the end-to-end canary release feature. You can implement an end-to-end canary release from a gateway to multiple backend applications. This way, canary traffic that has specific characteristics can always be routed to the canary environments of applications. This helps you test a version on multiple applications by using a canary release. This topic describes how to implement an end-to-end canary release by using different methods that are provided by Microservices Governance.

Implement an end-to-end canary release based on MSE cloud-native gateways

You can use an MSE cloud-native gateway to implement an end-to-end canary release on backend applications that are deployed in a Container Service for Kubernetes (ACK) cluster or the applications that are registered with an MSE Nacos instance. For more information, see Implement an end-to-end canary release based on MSE cloud-native gateways.

Implement an end-to-end canary release based on MSE Ingress gateways

You can use the end-to-end canary release feature provided by MSE Ingress gateways to implement end-to-end traffic control without the need to modify any business code. For more information, see Implement an end-to-end canary release based on MSE Ingress gateways.

Implement an end-to-end canary release based on self-managed Spring Cloud or Zuul gateways

You can use a self-managed Spring Cloud Gateway or Zuul gateway involved in microservices development to implement an end-to-end canary release on backend applications that are deployed in an ACK cluster or applications that are registered with an MSE Nacos instance. For more information, see Implement an end-to-end canary release based on self-managed Spring Cloud or Zuul gateways.

Use Kruise Rollouts to implement an MSE-based end-to-end canary release

You can use Kruise Rollouts to implement canary releases, blue-green deployments, and A/B testing based on traffic and canary release of instances. You can also use Kruise Rollouts together with Microservices Governance to implement a seamless canary release on applications of new versions during the service call. For detailed configurations, see Use Kruise Rollouts to implement MSE-based end-to-end canary releases.