[[["容易理解","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,["# GKE on-premises to control plane connectivity insights\n\nThis page describes the Network Analyzer insights for Google Kubernetes Engine (GKE)\non-premises to control plane connectivity. For information about all the\ninsight types, see [Insight groups and types](/network-intelligence-center/docs/network-analyzer/insight-groups-types).\n\nView insights in the Recommender API\n------------------------------------\n\nTo view these insights in the Google Cloud CLI or the Recommender API, use\nthe following insight type:\n\n- `google.networkanalyzer.container.connectivityInsight`\n\nYou need the following permissions:\n\n- `recommender.networkAnalyzerGkeConnectivityInsights.list`\n- `recommender.networkAnalyzerGkeConnectivityInsights.get`\n\nFor more information about using the Recommender API for\nNetwork Analyzer insights, see [Use the Recommender CLI and API](/network-intelligence-center/docs/network-analyzer/use-cli-recommender-api).\n\nGKE on-premises to control plane connectivity missing return route\n------------------------------------------------------------------\n\nThis analyzer verifies connectivity between your on-premises network\nand the GKE control plane.\n\nIf this analyzer infers that there is a route in your on-premises network that\ndelivers traffic to the control plane, the analyzer also verifies that the\nreturn route exists in the control plane's VPC network. This\ninsight is generated when a Cloud Router advertises the control plane's\nCIDR range to the on-premises network, but the custom route to the on-premises\nnetwork is not exported to the GKE cluster's\nVPC Network Peering. When this happens, the analyzer infers that your\non-premises network has a route to the control plane's VPC\nnetwork. However, the GKE control plane does not have a return\nroute to your on-premises network. If this is your intended network\nconfiguration, you can dismiss this insight.\n\nThis insight includes the following information:\n\n- **GKE cluster:** Name of the GKE cluster.\n- **Network:** Name of the network where the GKE cluster is configured.\n- **VPC Network Peering:** The name of the VPC peering configuration that connects your GKE cluster to the control plane.\n- **Associated Cloud Routers:** The list of Cloud Routers that are advertising the control plane's address range.\n\n### Related topics\n\nFor more information, see\n[Connecting to the control plane's private endpoint from on-premises networks](/kubernetes-engine/docs/how-to/private-clusters#cp-on-prem-routing).\n\n### Recommendations\n\n- Configure your VPC network to export its custom routes in the peering relationship to the control plane's VPC network."]]
