Scenarios
Currently, Cloud Native Gateway supports three types of service sources: registry (Polaris), container service (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 and locate corresponding service addresses for dynamic proxying. If your service uses private DNS, you can use Tencent Cloud Private DNS as a service source to implement private domain name resolution for services.
Prerequisites
The cloud-native gateway instance has been purchased. For details about related operations, see Create Gateway. Operation Steps
Adding a Service Source
2. In the left sidebar, choose Cloud Native Gateway > Instance Management. Select a gateway instance to go to its details page. In the left sidebar, select Service & Route. Click the Service Source tab. On the Service Source page, click New.
3. On the Create Service Source page, configure related parameters.
|
Source Type | Yes | Service source type, which can be registry, TKE, and private DNS. |
Attention:
Currently, Cloud Native Gateway supports new purchases via allowlist only for microservices scenarios, where it acts as the access layer for Polaris services. Other scenarios do not support new access. When accessing the console for non-qualifying scenarios, you will be redirected to the Polaris console.
When the service source is a registry, specify the following parameters:
|
Source Product | Yes | Source product, which supports TSF Registry and self-built registries. Registry types include Nacos, Consul, PolarisMesh, and TSF Registry. Note: TSF PolarisMesh is recommended. |
Instance selection | Yes | Registry instance where the backend service resides when the source product is TSF Registry. |
Source name | Yes | Enter the source name when the source product is a self-built registry. |
Access Address | Yes | 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. The format for each set is: http://IP address:{HTTP_PORT}, grpc://IP address:{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 or Polaris. |
When the service source is TKE, specify the following parameters:
|
Source Product | Yes | The source product supports TKE. |
Instance selection | Yes | 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.