When your microservices run across different backends -- ACK clusters, EDAS registries, and MSE Nacos instances -- you need a unified entry point to direct external HTTP traffic to the correct service. Enterprise Distributed Application Service (EDAS) allows you to configure Microservices Engine (MSE) gateway routes for applications that are deployed in a Kubernetes cluster, providing path-based, header-based, and parameter-based routing.
Prerequisites
Before you begin, make sure that you have:
An EDAS account with access to the EDAS console
At least one application deployed in a Kubernetes cluster managed by EDAS
An MSE cloud-native gateway associated with your Container Service for Kubernetes (ACK) cluster
(Optional) Domain names configured on the Domain Names page in the MSE console
Route matching rules
A route matches a request only when all conditions in its rule are met. Adding more conditions narrows the set of matched requests.
Path match types
| Match type | Behavior | Example |
|---|---|---|
| Prefix Match | Matches requests whose path starts with the specified value. | /user |
| Exact Match | Matches only when the request path is identical to the specified value. | /user |
| Regex Match | Matches requests whose path satisfies a regular expression. | A regular expression pattern |
Route evaluation order
When multiple routes can match a request, the gateway evaluates them in the following order:
Routes are evaluated in their display order on the MSE Gateway Routes page.
For path-based rules with the same match type, longer path values take higher priority. For example,
/api/v1/userstakes priority over/api.For header or query parameter rules, more specified parameters mean higher priority. For example, a route that matches both
X-Env: prodandX-Region: ustakes priority over a route that matches onlyX-Env: prod.
Supported backend service types
| Service source | When to use |
|---|---|
| ACK Container | Your destination service runs as a Kubernetes service in an ACK cluster. |
| EDAS Registration Center | Your destination service is registered in an EDAS registry. |
| MSE Nacos | Your destination service is registered on an MSE Nacos instance. |
Create a route
Log on to the EDAS console.
In the left-side navigation pane, choose Traffic Management > Application Routing > MSE Gateway Routing.
On the MSE Gateway Routes page, click Create Route.
In the Create Route panel, complete the Request Information step and click Next.
Configure the following parameters:
NoteA route matches only when all conditions in its rule are met.
Requests match routes in their display order on the Routes page in the MSE console.
Parameter Description Route Name Enter a name for the route. MSE Cloud Native Gateway Select a gateway from the drop-down list. To create a new gateway, click + Create an MSE cloud native gateway. Associated Domain Name Select one or more domain names configured on the Domain Names page in the MSE console. Match Rule Define how incoming requests are matched to this route. Path The URL path pattern to match. Select a match type (Prefix Match, Exact Match, or Regex Match) and specify the path value. See Path match types. Method HTTP methods to match. Leave blank to match all methods. Select multiple values to broaden the match scope. Header HTTP headers to match. Click + Request header to add conditions. More headers mean higher route priority. Request Parameter (Query) Query string parameters to match. Click + Request parameters to add conditions. More parameters mean higher route priority. In the Destination Service step, configure the backend service and click Save.
Parameter Description Service Source Select the type of backend service: EDAS Registration Center, MSE Nacos, or ACK Container. See Supported backend service types. MSE Nacos Instance Required only when Service Source is set to MSE Nacos. Select an MSE Nacos instance from the drop-down list. Destination Service Click + Add service and configure NameSpace, Application, Service, Port, and Weight (%). 
Apply traffic policies to a route
After you create a route, apply traffic management policies to control throttling, rewriting, headers, CORS, timeouts, and retries.
Log on to the EDAS console.
In the left-side navigation pane, choose Traffic Management > Application Routing > MSE Gateway Routing.
On the MSE Gateway Routes page, find your route and click Policy Settings in the Actions column.
Select a policy tab and click Configure policy.
| Policy | Reference |
|---|---|
| Throttling | Configure a throttling policy |
| Rewrite | Configure a rewrite policy |
| Header Settings | Configure a header setting policy |
| CORS | Configure a CORS policy |
| Expiration | Configure a timeout policy |
| Retry | Configure a retry policy |
Edit a route
Log on to the EDAS console.
In the left-side navigation pane, choose Traffic Management > Application Routing > MSE Gateway Routing.
On the MSE Gateway Routes page, find the route and click Edit in the Actions column.
Monitor a route
Log on to the EDAS console.
In the left-side navigation pane, choose Traffic Management > Application Routing > MSE Gateway Routing.
On the MSE Gateway Routes page, find the route and click Monitor in the Actions column.
On the monitoring page, view data across three tabs. Use the time range selector in the upper-right corner to filter data on each tab.
Tab Data shown Global Kanban Global monitoring data for the selected gateway. Business TOP list Top-ranked workloads. Access Center User traffic data for the gateway. 
How it works
An MSE cloud-native gateway consists of two components:
Control plane: Monitors Ingresses, Ingress classes, and services in an associated ACK cluster, then sends parsed resource configurations to the data plane in real time.
Data plane: Implements traffic governance. The data plane processes incoming requests based on governance rules from the control plane and forwards them to the correct backend service.
An MseIngressConfig is a CustomResourceDefinition (CRD) that is provided by MSE Ingress Controller. MSE Ingress Controller creates gateways based on the MseIngressConfigs CRD.