tencent cloud

Service Registry and Governance

Service Source

PDF
Focus Mode
Font Size
Last updated: 2026-05-07 17:46:48

Scenarios

Currently, the cloud-native gateway supports three types of service sources: registry (Polaris), TKE, and private DNS. This document describes how to add a container cluster with deployed backend services or a registry with registered backend services to the gateway's service sources. This enables the gateway to obtain service lists, locate corresponding service addresses, and implement dynamic proxying. If your service uses private DNS, you can use Tencent Cloud Private DNS as the service source to achieve private domain name resolution for the service.

prerequisite

A cloud-native gateway instance has been purchased. For details about related operations, see Gateway Instance Management.

Operation steps

Adding a Service Source

1. Log in to the TSF console.
2. In the left sidebar, choose Cloud Native Intelligent Gateway > Instance Management. Select a gateway instance to go to its details page. Click the Service Source tab. On the Service Source page, click New.
3. On the Create Service Source page, configure related parameters.
parameter
Required
Remarks
Source Type
Create and bind policy Query instance Reset instance access password
Service source type, which can be registry, TKE, and private DNS.
Note:
Currently, Cloud Native Gateway only supports adding user accounts to the purchase allowlist in microservice scenarios, where it serves as the service access layer for Polaris (Polaris). New access is not supported in other scenarios. When accessing the console in non-supported scenarios, users will be redirected to the Polaris (Polaris) console.
When the service source is a registry, specify the following parameters:
parameter
Required
Remarks
Source Product
Create and bind policy Query instance Reset instance access password
Source product, which can be TSF Registry or self-built registry. Registry types include Nacos, Consul, PolarisMesh, and TSF Registry.
Note: TSF PolarisMesh is recommended.
Instance
Create and bind policy Query instance Reset instance access password
Registry instance where the backend service resides when the source product is TSF Registry.
source name
Create and bind policy Query instance Reset instance access password
Enter the source name when the source product is a self-built registry.
Access Address
Create and bind policy Query instance Reset instance access password
Enter the access address when the source product is a self-built registry. Use line breaks to separate multiple addresses. The access address writing method varies depending on the registry:
Self-built Nacos: Enter the domain name or IP:Port.
Self-built Consul: Enter the domain name or IP:Port.
Self-built PolarisMesh: Enter the http and grpc access addresses as a set of access addresses. The format for each set is: http://IP:{HTTP_PORT}, grpc://IP:{GRPC_PORT}.
userName
No
Enter the access username if registry authentication is enabled for Nacos.
password
No
Enter the access password if registry authentication is enabled for Nacos.
Access Token
No
Enter the Access Token if registry authentication is enabled for Consul and Polaris.
When the service source is TKE, specify the following parameters:
parameter
Required
Remarks
Source Product
Create and bind policy Query instance Reset instance access password
The source product supports TKE Container Service.
Instance
Create and bind policy Query instance Reset instance access password
Select the container cluster where the backend service resides.
When the service source is the private DNS, select Private DNS to use it for domain name resolution.
4. After a service source is added, view the service source list. If information about the newly added service source is included, the service source is added successfully.

Deleting a Service Source

Click Delete in the Operation column of a service source. In the displayed dialog box, click Confirm.
Note
A service source associated with services cannot be deleted. To delete the service source, you should delete the services first.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback