이 분석기가 온프레미스 네트워크에 컨트롤 플레인으로 트래픽을 전달하는 경로가 있다고 유추할 경우에는 분석기가 또한 반환 경로가 컨트롤 플레인의 VPC 네트워크에 있는지도 확인합니다. 이 통계는 Cloud Router가 컨트롤 플레인의 CIDR 범위를 온프레미스 네트워크에 공지할 때 생성되지만, 온프레미스 네트워크에 대한 커스텀 경로가 GKE 클러스터의 VPC 네트워크 피어링으로 내보내지지 않습니다. 이 경우 분석기는 온프레미스 네트워크에 컨트롤 플레인의 VPC 네트워크에 대한 경로가 있다고 유추합니다. 그러나 GKE 컨트롤 플레인에는 온프레미스 네트워크에 대한 반환 경로가 없습니다. 이것이 의도된 네트워크 구성이면 이 통계를 닫을 수 있습니다.
이 통계에는 다음 정보가 포함됩니다.
GKE 클러스터: GKE 클러스터의 이름입니다.
네트워크: GKE 클러스터가 구성된 네트워크의 이름입니다.
VPC 네트워크 피어링: GKE 클러스터를 컨트롤 플레인에 연결하는 VPC 피어링 구성의 이름입니다.
연결된 Cloud Router: 컨트롤 플레인의 주소 범위를 공지하는 Cloud Router 목록입니다.
[[["이해하기 쉬움","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(UTC)"],[],[],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."]]
