Meshery Docs ยท ๐ Extensibility & Reference
ErrUntrustedClusterEndpointCode-11349
Component: library / meshkit
Code: meshkit-11349 (ErrUntrustedClusterEndpointCode-11349)
Severity: Alert
Short description
Refusing to send cloud credentials to an unrecognized cluster endpoint
Long description
Probable cause
- The kubeconfig server is not an EKS or GKE control plane endpoint, for example a proxy, a load balancer, or a host controlled by whoever wrote the kubeconfig
- The kubeconfig disables TLS verification (insecure-skip-tls-verify), uses http, or routes the connection through proxy-url
- For EKS, the exec stanza's --region differs from the region in the endpoint host name
- For a GKE IP endpoint, the kubeconfig has no certificate-authority data, or the GKE API did not confirm that this IP and CA certificate belong to a cluster in a trusted project (the ADC project, GOOGLE_CLOUD_PROJECT or GOOGLE_PROJECT)
Suggested remediation
- Use the cluster endpoint written by aws eks update-kubeconfig or gcloud container clusters get-credentials, with TLS verification enabled
- For a GKE IP endpoint, grant the Meshery process container.clusters.get or container.clusters.list on the cluster project, and set GOOGLE_CLOUD_PROJECT to that project unless it is the ADC project
- Alternatively install the exec credential plugin named in the kubeconfig on the Meshery host's PATH, so it authenticates instead
- To keep the exec plugin for a context, disable in-process cloud auth for that context's kubeconfig user; every context sharing that user switches with it
- If the Meshery server cannot hold cloud credentials, deploy the Meshery Operator into the cluster instead