tencent cloud

Cloud Native Intelligent Gateway

DokumentasiCloud Native Intelligent GatewayCloud Native GatewayOperation GuideService RoutingServices

Services

Unduh
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-09-22 18:27:33
Diterjemahkan oleh AI

Scenarios

You need to add services to Cloud Native Intelligent Gateway so that the gateway can locate the corresponding service addresses for dynamic proxying. Cloud Native Intelligent Gateway supports adding services of several types, including Kubernetes services, registries, IP address lists, domain names/IP addresses, private domain names, and SCF. This document describes how to add services to Cloud Native Intelligent Gateway.

Operation Steps

Adding a Service

1. Log in to the TSF console.
2. In the left sidebar, click Cloud Native Gateway to go to the instance list. Then, click the target instance ID/Name to enter the instance details page.
3. In the left sidebar, click Service & Route. Then, click the Service tab. Finally, in the service list, click New.
4. On the Create Service page, configure related parameters.
Parameter
Required
Description
Service Name
Yes
Enter the service name.
Service type
Yes
Service type, which supports multiple types such as K8S service, registry, IP list, domain name/IP, private domain name, and SCF.
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.

Kubernetes Service

When the service source is the Kubernetes service, specify the following parameters:
Parameter
Required
Description
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
No
Request path of the backend service.
Service port
No
Port of the backend service, ranging from 1 to 65535.
Timeout Time
Yes
Maximum timeout period for connection establishment, data writing, and reading responses from the backend service.
Number of retries
Yes
Maximum number of retries for establishing a connection to the backend service.

Registry

When the service source is a registry, specify the following parameters:
Parameter
Required
Description
Service Source
Yes
Select the created service source.
Namespace
Yes
When the source product is Nacos/Polaris, enter the namespace ID. Note: For the default Nacos 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: Separate the Nacos group and the service name with an underscore "_".
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
No
Request path of the backend service.
Timeout Time
Yes
Maximum timeout period for connection establishment, data writing, and reading responses from the backend service.
Number of retries
Yes
Maximum number of retries for establishing a connection to the backend service.

IP List

When the service type is IP list, specify the following parameters:
Parameter
Required
Description
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
No
Request path of the backend service.
Timeout Time
Yes
Maximum timeout period for connection establishment, data writing, and reading responses from the backend service.
Number of retries
Yes
Maximum number of retries for establishing a connection to the backend service.

Domain Name/IP Address

When the service type is domain name/IP address, specify the following parameters:
Parameter
Required
Description
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
No
Request path of the backend service.
Timeout Time
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 to the backend service.

SCF

When the service type is SCF, specify the following parameters:
Parameter
Required
Description
Function Type
Yes
Event function or web function.
Namespace
Yes
Select the namespace where the function is stored.
Function
Yes
Select a 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.
Response integration
No
Whether to enable response integration.
Base64 encoding
No
Whether to perform Base64 encoding on the response.
Timeout Time
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 to the backend service.

Private DNS

When the service source is the private domain name, specify the following parameters:
Parameter
Required
Description
Service Source
Yes
Select the created Private DNS.
Private DNS
Yes
Enter the private domain name of the service.
Service port
No
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
No
Request path of the backend service.
Timeout Time
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 to the backend service.
1. (Optional) Configure advanced parameters.
Load Balancing Algorithm: Select Polling or Least Connections.
Slow Start: After this feature is enabled, the nodes corresponding to the service gradually increase their weight from 1 to the target value during the slow start period. If the gateway edition is low, this feature may not be supported. We recommend that you go to the instance basic information page to upgrade the gateway edition. For details, see Upgrading Gateway Edition.
Note:
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"

2. After the addition, the newly added service will appear in the service list. Click Service ID/Name to view detailed service information.

Editing a 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.

Topik sebelumnya: Deleting a Gateway InstanceTopik selanjutnya: Route

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan

Search
    Enter keywords to search documentation