[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間: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"]]