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：
Resource Creation via YAML
You can use the console UI to create, delete, update, and view Gateways, VirtualServices, and DestinationRules.
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.