DocsICP FilingConsole
Documentation
Home Page Microservices Engine User Guide Cloud-native gateways Route management Services Add a service

Add a service

Updated at:
Copy as MD
Product
My Favorites

Add your services to the gateway to make them available for routing. This allows the gateway to retrieve their service addresses. MSE Cloud-native Gateway supports adding services from various sources, including Container Service for Kubernetes (ACK), MSE Nacos, MSE Zookeeper, EDAS registries, SAE registries, SAE Kubernetes, fixed addresses, DNS domain names, and Function Compute (FC).

Procedure

  1. Log on to the MSE Gateway Management Console, and in the top menu bar, select a region.

  2. In the navigation pane on the left, choose Cloud-native Gateway > Gateways.

  3. On the Gateways page, click the name of the target gateway.

  4. In the navigation pane on the left, choose Routes, and then click the Services tab.

  5. Click Add service. In the Add service panel, configure the Service Sources, configure the related parameters, and then click OK.

    Note

    The cloud-native gateway does not modify your requests. When a request is forwarded to a backend service that uses a domain name, the Host header is not rewritten to the configured domain name. If you need to configure domain name rewriting, see Configure a rewrite policy.

Service parameters

Note

  • Add a service from Container Service for Kubernetes (ACK): When you add a service from ACK, the gateway retrieves the service list from the specified ACK or ACK Serverless cluster and adds these services and their backend node endpoints to the gateway.

  • Add a service from a fixed address: If the service does not have a service discovery mechanism, you must manually add the service's backend node endpoints.

  • Add a service from a DNS domain name: The cloud-native gateway uses DNS query results as backend service addresses.

Service source

Parameter

Description

Container Service for Kubernetes (ACK)

Note

When you add a service from ACK as a service source, the gateway retrieves the service list from the specified ACK or ACK Serverless cluster and adds these services and their backend node endpoints to the gateway.

Namespaces

Select the namespace of the cluster. By default, services in the arms-prom, kube-system, and mse-pilot namespaces are not displayed.

Services

Select a service from the list. By default, services with names that start with consumers are not displayed.

MSE Nacos

Specify Nacos instance

Nacos source list

Select a Nacos source instance. After you specify an instance, the system retrieves service and provider address information exclusively from that instance.

Namespaces

Select the namespace of the cluster. By default, services in the arms-prom, kube-system, and mse-pilot namespaces are not displayed.

Services

Select a service from the list. By default, services with names that start with consumers are not displayed.

Fixed address

Note

If the service does not have a service discovery mechanism, you must manually add the service's backend node endpoints.

Service name

Enter a custom name for the service.

Service address

The backend node endpoints for the service. The format is <backend node IP>:<service port>. Separate multiple endpoints with line breaks.

TLS mode

Select a TLS mode from the drop-down list. By default, this parameter is set to Disabled.

  • Close: TLS is not required to access the service.

  • One-way TLS: Required for accessing the service over HTTPS.

  • Mutual TLS (mTLS): Enable mutual TLS (mTLS) if you require two-way authentication.

DNS domain name

Note

The cloud-native gateway uses DNS query results as backend service addresses.

Service name

Enter a custom name for the service.

Service port

The service port associated with the domain name. Valid values: 1 to 65535.

Domain names

Enter a DNS domain name, such as www.aliyun.com. Separate multiple domain names with line breaks.

TLS mode

Select a TLS mode from the drop-down list. By default, this parameter is set to Disabled.

  • Close: TLS is not required to access the service.

  • One-way TLS: Required for accessing the service over HTTPS.

  • Mutual TLS (mTLS): Enable mutual TLS (mTLS) if you require two-way authentication.

More settings

DNS servers

Configure DNS servers for the service. For more information, see Configure a DNS server.

Note

If this parameter is not configured, the system's default DNS server is used.

MSE Zookeeper

Services

Select a service from the list.

EDAS registry

Microservices namespace

Select the microservices namespace where the service resides.

Services

Select a service from the list.

SAE registry

Namespaces

Select the namespace where the service resides.

Services

Select a service from the list.

Function Compute (FC)

Service name

Select the name of the Function Compute service.

Version or alias

Select a version or alias of the function.

Functions

Select a function from the list.

SAE Kubernetes

Note

The service list displays SAE applications that are accessible via a K8s Service Name.

Namespaces

Select the namespace of the cluster.

Services

Select a service from the list.

Verify the result

Return to the Route management page and click the Service tab to view the service information. The service has been added successfully if its details, including its Service name, Service address, and Service Sources, are displayed.

Related documentation

After you add a service, you can manage it. For more information, see Manage services.

Previous：ServicesNext：Manage services