- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- FAQs
- Overview
- Permissions
- Pod Startup Fails Because the Envoy Sidecar Is Unready
- Envoy Status Code 431 "Request Header Fields Too Large" Is Returned
- Envoy Converts Headers to Lowercase
- Headless Service-related FAQs
- Istio-init Crashes
- VirtualService Does Not Take Effect
- Inappropriate VirtualService Route Matching Order
- Failed to Access an Ingress Gateway from the Public Network
- Parsing Fails After Smart DNS Is Enabled
- Locality Load Balancing Does Not Take Effect
- Client Status Code 426 "Upgrade Required" Is Returned
- Sidecars Are Not Automatically Injected
- Circuit Breaking Does Not Take Effect
- 404 Is Returned During Access to a StatefulSet's Pod IP Address
- Service Is Abnormal Due to a Retry Policy
- Incomplete Call Tracing Information
- TCM Policy
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- FAQs
- Overview
- Permissions
- Pod Startup Fails Because the Envoy Sidecar Is Unready
- Envoy Status Code 431 "Request Header Fields Too Large" Is Returned
- Envoy Converts Headers to Lowercase
- Headless Service-related FAQs
- Istio-init Crashes
- VirtualService Does Not Take Effect
- Inappropriate VirtualService Route Matching Order
- Failed to Access an Ingress Gateway from the Public Network
- Parsing Fails After Smart DNS Is Enabled
- Locality Load Balancing Does Not Take Effect
- Client Status Code 426 "Upgrade Required" Is Returned
- Sidecars Are Not Automatically Injected
- Circuit Breaking Does Not Take Effect
- 404 Is Returned During Access to a StatefulSet's Pod IP Address
- Service Is Abnormal Due to a Retry Policy
- Incomplete Call Tracing Information
- TCM Policy
- Glossary
Mesh Mode
Managed mode
Managed mode means that the control plane components of a mesh are managed by Tencent Cloud Mesh, and the Tencent Cloud Mesh team is responsible for ensuring the availability of the control plane of the mesh, eliminating deployment and operations costs of control plane resources for a user. The user only needs to focus on the use of the mesh. Currently, managed meshes are not separately billed, and therefore it is recommended that you choose the managed mode preferentially.
Feature differences between a managed mesh and a stand-alone mesh
Capability | Managed Mesh | Stand-alone Mesh |
Operations-free control plane | Support | Not support |
Login to a control plane host | Not support | Support |
Mesh management through Istioctl | Not support | Support |
Stand-alone mode
Stand-alone mode means that the control plane components of a mesh are deployed in a cluster specified by a user and are maintained by the user. In this mode, the user has greater autonomy, but also needs to assume a greater availability risk. Currently, a stand-alone mesh can be used after being added to an allowlist. If you need to use a stand-alone mesh, contact after-sales personnel or submit a ticket.
Quota Limits
Maximum number of meshes by default: 20
Maximum number of clusters in a single mesh: 10
Maximum number of regions in a single mesh: 3
To use more resources, submit a ticket to apply for them.
Yes
No
Was this page helpful?