How to Implement Full‑Chain Traffic Gray on Kubernetes Ingress with MSE

Background

As cloud‑native technologies become mainstream, many applications migrate to Kubernetes for immutable infrastructure, elastic scaling, and rapid digital transformation. Managing external access to services is standardized through the Ingress resource, which routes traffic into the cluster.

Why Ingress Is Needed

Kubernetes exposes traffic via NodePort, LoadBalancer, and Ingress. NodePort suffers from single‑point and port‑exhaustion issues, while LoadBalancer lacks routing capabilities. Ingress provides native routing definitions and acts as a manager for multiple backend Services, with implementations such as Nginx Ingress Controller.

Full‑Chain Traffic Gray Requirement

In microservice architectures, a request may traverse several services, each possibly having a gray environment. To keep a request within gray environments throughout the chain—even when some services lack a gray version—MSE offers a full‑link gray capability that requires no code changes.

Key Elements for Full‑Link Gray

Label Routing : Group service nodes by label name/value, allowing consumers to target a specific subset of nodes.

Node Tagging : Add labels to Pods in the Deployment spec; the Service discovers Pods via Endpoints, exposing those labels as metadata.

Traffic Coloring : Mark requests at the source (frontend or gateway) with a gray identifier; if a downstream service lacks the identifier, the system automatically colors the traffic so subsequent hops route to gray instances.

MSE Lane Concept

MSE introduces “lane” and “lane group” to realize the three elements above. An example architecture includes Nginx‑Ingress, Spring Cloud microservices, and Nacos for service discovery, with three hops: transaction, product, and inventory services.

Implementation Steps

Configure the Ingress controller to use MSE by adding two entries to the Nginx Ingress ConfigMap:

use-mse: true
mse-app-name: ingress-canary-test

Deploy the ConfigMap; the MSE console will display an entry named ingress-canary-test.

Define lane rules in the MSE console to match traffic based on labels, tags, or request attributes, thereby directing colored traffic to gray pods.

Verify the gray routing by observing traffic distribution in the MSE console.

Verification and References

After configuring lane rules, traffic matching the specified characteristics is routed to the corresponding lane. The MSE Ingress, a native implementation compatible with both Ingress and Istio, offers stronger performance and built‑in traffic governance. For detailed Java‑application steps, refer to the Alibaba Cloud documentation linked below.

https://help.aliyun.com/document_detail/460275.html

https://help.aliyun.com/document_detail/460375.html