[[["容易理解","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,["# Troubleshoot Cloud Service Mesh GKE service mesh deployments\n============================================================\n\nThis guide contains information for resolving issues with Gateway API service\nmesh deployments.\n\nInformation in the `status` field\n---------------------------------\n\nAll Gateway API resources have a `status` field that reflects the status of\nresources from the controller perspective. In addition to the `status` field,\nthe controller appends events to Gateway API resources to provide information\nabout its operations on those resources.\n\nFor example, use the following commands to inspect the status and events of a\n`TDMesh`: \n\n```\nkubectl describe tdmesh td-mesh\n```\n\nThe output is similar to the following: \n\n```\n...\nStatus:\n Conditions:\n Last Transition Time: 1970-01-01T00:00:00Z\n Message: Waiting for controller\n Reason: NotReconciled\n Status: False\n Type: Scheduled\nEvents:\n...\n```\n\nThe previous status indicates that the controller has not started to reconcile\nthis particular mesh. If this status lasts for more than 5 minutes with no\nevents appended, read the following section,\n[Controller does not seem to reconcile a `TDMesh` resource](/service-mesh/legacy/gateway/gke-gateway-overview#controller-issue)\nto further troubleshoot the issue.\n\nYou can use a similar method to debug issues related to other resources, such as\n`HTTPRoute`, `TCPRoute`, and other routing resources.\n\nUsually, the statuses and events indicate the underlying issue.\n\n### Controller does not seem to reconcile a `TDMesh` resource\n\nTo diagnose the issue, confirm that a `gke-td` `GatewayClass` exists: \n\n```\nkubectl get gatewayclasses\n```\n\nThe output should include a `GatewayClass` named `gke-td`. \n\n```\nNAME CONTROLLER\ngke-td networking.gke.io/gateway\n```\n\nIf a `GatewayClass` with that name is not returned, follow\n[Install the required custom resource definitions](/service-mesh/legacy/gateway/prepare-gateway#install-crds)\nto confirm all required CRDs are installed in the config cluster, then reenable\nthe hub feature for the Cloud Service Mesh Google Kubernetes Engine service mesh with the\nfollowing commands:\n\n1. Disable the feature:\n\n ```\n gcloud container hub ingress disable\n ```\n2. Re-enable the feature:\n\n ```\n gcloud container hub ingress enable \\\n --config-membership=/projects/PROJECT_ID/locations/global/memberships/gke-1\n ```"]]
