[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["Resolving cleanup issues\n\nThis page explains how to resolve issues with Cloud Service Mesh managed control plane\nwhen using the `TRAFFIC_DIRECTOR` implementation.\n\nClean up synthetic services\n\nWhen using the `TRAFFIC_DIRECTOR` control plane implementation, Cloud Service Mesh\ncreates synthetic Kubernetes services to support subset. These services are\nlabeled with `istio.io/owned-by:gsmconfig.gke.io`.\n\nWhen you unregister a cluster from a Google Cloud fleet, Cloud Service Mesh\nmight not be able to remove these synthetic Kubernetes services.\n\nTo mitigate this issue, you can manually remove synthetic Kubernetes services in\nall namespaces by running the following command: \n\n kubectl delete service -l istio.io/owned-by=gsmconfig.gke.io -A\n\nClean up network endpoint groups annotations\n\nWhen using the `TRAFFIC_DIRECTOR` control plane implementation, Cloud Service Mesh\ncreates network endpoint groups by adding `cloud.google.com/neg` annotations to\nservices for load balancing.\n\nWhen you unregister a cluster from a Google Cloud fleet, Cloud Service Mesh\nmight not be able to remove these annotations to clean up the network endpoint\ngroups.\n\nTo mitigate this issue, you can manually remove the `cloud.google.com/neg`\nannotations from services in all namespaces. \n\n service_names=($(kubectl get service -A -o jsonpath='{.items[*].metadata.name}'))\n for service in \"${service_names[@]}\"; do\n kubectl annotate service $service -A cloud.google.com/neg-\n done"]]