Service Mesh Troubleshooting¶

This page will continuously collect and sort out the errors that may be caused by the environment or irregular operations during the use of the service mesh, as well as the problem analysis and solutions for some errors encountered during the use of the service mesh. If you encounter problems with the use of the service mesh, please review this troubleshooting manual first.

Create Mesh¶

The service mesh supports 3 modes:

• Hosted mode: the control plane and the data plane are separated, and a virtual cluster is created to store managed Istio CRD resources

  When creating a hosted mesh, a managed control plane virtual cluster API Server will be created in the managed control plane cluster to store Istio CRD resources; In principle, only one hosted mesh is allowed in a DCE environment. The global cluster of DCE contains Istio-related components that global management depends on. It is not allowed to use this cluster to create a hosted mesh, and you can use an external mesh to create it during demo.

• Dedicated mode: the control plane and the data plane are deployed in one cluster

• External mode: the cluster to which it belongs must contain istio-related components

Common failure cases when creating a mesh are as follows:

• Cannot Find Cluster When Creating Mesh
• Mesh Creation Stuck in "Creating" and Eventually Fails
• Unable to Delete Abnormal Mesh
• Failed to Add Cluster to Hosted Mesh
• Istio-ingressgateway Issues When Adding Cluster to Hosted Mesh
• Unable to Unbind Mesh Space Properly
• DCE 4.0 Integration Issue Tracking
• Namespace Sidecar Configuration Conflicts with Workload Sidecar
• MultiCloud Interconnect Issues in Hosted Mesh
• Sidecar Consuming Large Amount of Memory
• Unknown Cluster Appears in Cluster List During Mesh Creation
• Handling Expired Certificates for Hosted Mesh APIServer

Other Common Issues¶

• Common 503 Errors in Service Mesh
• How to Make an Application Listening on localhost in a Cluster Accessible by Other Pods

Comments