tencent cloud

Service Registry and Governance

ドキュメントService Registry and GovernanceCloud Native GatewayOperation GuideService Routeservice

service

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-05-07 17:21:35

Scenarios

Add services to the cloud-native gateway. This enables the gateway to locate the corresponding service addresses and perform dynamic proxying. The cloud-native gateway supports adding several types of services, including K8S services, registries, IP address lists, domain names/IP addresses, private domain names, and SCF. This document describes how to add services to the cloud-native gateway.

operation steps

Add service

1. Log in to the TSF console.
2. In the left sidebar, click Service & Route, select an instance at the top of the page, click the Service tab, and click Create in the service list.
3. On the Create Service page, configure related parameters.
parameter
Required
Remarks
service name
Yes
Enter the service name.
service type
Yes
Service type. Registry is supported, and other service types are not supported.
Note:
Currently, the cloud-native gateway supports new purchases with allowlist only for the microservices scenario, where it acts as the Polaris (North Star) service access layer. It does not support new access for other scenarios. When you access the console for scenarios other than those described above, you are redirected to the Polaris (North Star) console.
Kubernetes Service
Registry
IP list
Domain Name/IP Address
SCF
Private DNS
When the service source is the Kubernetes service, specify the following parameters:
parameter
Required
Remarks
Service Source
Yes
Select the created TKE source.
namespace
Yes
Enter the namespace name.
service list
Yes
Enter the list of container services that need to be accessed. Use line breaks to separate the services.
Service Protocol
Yes
Protocol used by the gateway to request backend services, which can be HTTP/WS, HTTPS/WSS, TCP, and UDP.
Service Path
Yes
Request path of the backend service.
Service Port
No
Port of the backend service, ranging from 1 to 65535.
Timeout Period
Yes
Maximum timeout period from connection establishment and writing and reading data to a response from the backend service.
Number of Retries
Yes
Maximum number of retries for establishing a connection with the backend service.
When the service source is a registry, specify the following parameters:
parameter
Required
Remarks
Service Source
Yes
Select the created service source.
namespace
Yes
When the source product is Nacos/Polaris, enter the namespace ID. Note: For the Nacos default namespace, enter empty_ns. When the source product is TSF Registry, select a namespace from the dropdown list.
service list
Yes
When the source product is Nacos/PolarisMesh/Consul, enter the list of services to be accessed, which are separated with line breaks. The service list writing method varies depending on the registry.
Nacos: {Nacos group}__{service name} Note: Use two underscores "_" to separate the Nacos group and the service name.
Consul: {service name}
PolarisMesh: {service name}
When the source product is TSF Registry, select a microservice name from the dropdown list.
Service Protocol
Yes
Protocol used by the gateway to request backend services, which can be HTTP/WS, HTTPS/WSS, TCP, and UDP.
Service Path
Yes
Request path of the backend service.
Timeout Period
Yes
Maximum timeout period from connection establishment and writing and reading data to a response from the backend service.
Number of Retries
Yes
Maximum number of retries for establishing a connection with the backend service.

When the service type is IP list, specify the following parameters:
parameter
Required
Remarks
Address List
Yes
Enter the IP address, port, and weight information of the backend service node.
CVM Elastic Scaling
No
When it is enabled, Cloud Native API Gateway is automatically associated with the Cloud Virtual Machine (CVM) instance of the selected scaling group.
Scaling group: Select the elastic scaling group in the same VPC. After association, Cloud Native API Gateway creates a lifecycle hook in the elastic scaling group and an elastic scaling command in CVM > My Commands. Scaling fails if the preceding resources are modified or deleted.
Scaling group port: Enter the scaling group port.
Service Protocol
Yes
Protocol used by the gateway to request backend services, which can be HTTP/WS, HTTPS/WSS, TCP, and UDP.
Service Path
Yes
Request path of the backend service.
Timeout Period
Yes
Maximum timeout period from connection establishment and writing and reading data to a response from the backend service.
Number of Retries
Yes
Maximum number of retries for establishing a connection with the backend service.

When the service type is domain name/IP address, specify the following parameters:
parameter
Required
Remarks
service address
Yes
Enter an IP address or domain name, for example, 10.0.0.1 or www.tencent.com.
Service Port
Yes
Port of the backend service, ranging from 1 to 65535.
Service Protocol
Yes
Protocol used by the gateway to request backend services, which can be HTTP/WS, HTTPS/WSS, TCP, and UDP.
Service Path
Yes
Request path of the backend service.
Timeout Period
Yes
Maximum timeout period from connection establishment and writing and reading data to a response from the backend service.
Number of Retries
Yes
Maximum number of retries for establishing a connection with the backend service.

When the service type is SCF, specify the following parameters:
parameter
Required
Remarks
Function Type
Yes
Event function or web function.
namespace
Yes
Select the namespace where the function is stored.
function
Yes
Select the function.
Version/Alias
Yes
Select the service version or alias of the function.
CAM authentication
Yes
It is enabled by default. The gateway forwards requests to SCF for Cloud Access Management (CAM) authentication.
Timeout Period
Yes
Maximum timeout period from connection establishment and writing and reading data to a response from the backend service.
Number of Retries
Yes
Maximum number of retries for establishing a connection with the backend service.

When the service source is the private domain name, specify the following parameters:
parameter
Required
Remarks
Service Source
Yes
Select the created Private DNS.
Private DNS
Yes
Fill in the private domain name for the write service.
Service Port
Yes
Enter the list of container services that need to be accessed. Use line breaks to separate the services.
Service Protocol
Yes
Protocol used by the gateway to request backend services, which can be HTTP/WS, HTTPS/WSS, TCP, and UDP.
Service Path
Yes
Request path of the backend service.
Timeout Period
Yes
Maximum timeout period from connection establishment and writing and reading data to a response from the backend service.
Number of Retries
Yes
Maximum number of retries for establishing a connection with the backend service.
Remarks:
1. The gateway only parses SRV records, A records, and CNAME records.
2. If a port is specified for an SRV record, the console input port will overwrite the port of the SRV record.
4. (Optional) Configure advanced parameters.
Load Balancing Algorithm: Select Polling or Least Connections.
Slow Start: After it is enabled, the service node gradually increases its weight from 1 to the target value within the slow startup time. This feature may be unavailable if an earlier engine version is used. You are advised to upgrade the engine version on the Basic Information page of the instance.
Remarks:
You can configure slow start and add annotations by modifying the YAML file in the TKE cluster.
annotations:
    tse.konghq.com/TSE-Upstream-SlowStart: "30"
5. After addition, the newly added service will appear in the list. Click the service ID/name to view detailed service information.

editing service

Click Edit in the Operation column of a service, modify the service information, and click Confirm in the displayed dialog box.

Deleting a Service

Click Delete in the Operation column of a service, and click Confirm in the displayed dialog box.
前の記事へ: Deleting a Gateway Instance次の記事へ: Route

ヘルプとサポート

この記事はお役に立ちましたか？

フィードバック