Resolving installation issues
This section explains common Cloud Service Mesh problems and how to resolve them. If you need additional assistance, see Getting support.
Failed installation due to missing meshtelemetry.googleapis.com API
If your installation fails due to the enablement of
meshtelemetry.googleapis.com, ensure you have removed the enablement of
meshtelemetry.googleapis.com from your installation process. This API is no
longer required and has been deprecated. For more information, see the full list
of
required APIs.
Failed installation because mdp-controller is not ready
If your installation fails with error code REVISION_FAILED_PRECONDITION or
an error message saying the mdp-controller is not ready,
ensure that your cluster has nodes which can be used to provision MDP controller.
MDP controller is required to onboard to Cloud Service Mesh.
A common issue that can prevent a node from being used for MDP controller
deployment is if you have node taints configured.
You can run the following command to verify the node taints you have configured:
kubectl describe node NODE_NAME