tencent cloud

All product documents
Tencent Cloud Mesh
DocumentationTencent Cloud MeshOperation GuideTraffic ManagementOverview
Overview
Download PDF
Last updated: 2023-12-26 11:48:08
Overview
Last updated: 2023-12-26 11:48:08
Download PDF

Traffic Management Model of Tencent Cloud Mesh

Tencent Cloud Mesh is fully compatible with Istio's native traffic management CRDs Gateway, VirtualService, and DestinationRule, and presents the native traffic management syntax as a product. The following figure shows the traffic management model of Tencent Cloud Mesh:

Tencent Cloud Mesh uses Gateway, VirtualService, and DestinationRule to manage traffic.
Gateway: defines the port, listening rule, and certificate configurations of a gateway. Gateways and gateway configurations are in a one-to-many relationship. The Gateway specifies a gateway to which the configurations are to be delivered through the selector field.
VirtualService: defines routing rules and traffic operation rules for a specified host. The VirtualService specifies a bound domain name through the hosts field. It can specify that traffic comes from a gateway or an internal component of a mesh.
DestinationRule: defines versions and traffic policies of a service. The traffic policies include load balancing, health check, and connection pools. Services and DestinationRules are in a one-to-one binding relationship.

Traffic Management Configuration Methods

At present, Tencent Cloud Mesh provides the following two methods of configuring Gateways, VirtualServices, and DestinationRules：
Console UI Configuration
Resource Creation via YAML
You can use the console UI to create, delete, update, and view Gateways, VirtualServices, and DestinationRules.
Creating a Gateway

Creating a VirtualService

Creating a DestinationRule: As DestinationRules and services are in a one-to-one binding relationship, operations of creating and managing DestinationRules are performed on the service details page.


You can create Istio or Kubernetes resources by clicking Create via YAML in the upper right corner of the mesh management window. If the YAML to be submitted contains a Kubernetes resource and the current mesh manages multiple clusters, you need to select a destination cluster to which the YAML-created resource is submitted.

Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Contact Us
Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

Submit a Ticket
7x24 Phone Support
Hong Kong, China
+852 800 906 020 (Toll Free)
United States
+1 844 606 0804 (Toll Free)
United Kingdom
+44 808 196 4551 (Toll Free)
Canada
+1 888 605 7930 (Toll Free)
Australia
+61 1300 986 386 (Toll Free)
EdgeOne hotline
+852 300 80699
More local hotlines coming soon