[[["易于理解","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,["# GKE control plane connectivity insights\n\nThis page describes the Network Analyzer insights for\nGoogle Kubernetes Engine (GKE) control plane connectivity. For information about\nall the insight types, see\n[Insight groups and types](/network-intelligence-center/docs/network-analyzer/insight-groups-types).\n\nNetwork Analyzer detects connectivity issues caused by configurations when\nthe GKE control plane initiates a connection with a\nGKE node.\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 control plane to node connectivity blocked by routing issue\n---------------------------------------------------------------\n\nThis insight indicates that the connection from the GKE control\nplane to the node is blocked by a routing issue. This insight includes the\nfollowing information:\n\n- **GKE cluster:** The name of the GKE cluster.\n- **Control plane endpoint:** The IP address of the endpoint.\n- **Network:** The name of the network where the GKE cluster is configured.\n\nIn private clusters, the control plane's VPC network is connected\nto your cluster's VPC network with\n[VPC Network Peering](/vpc/docs/vpc-peering). Traffic is routed to the control plane by using a\n[peering subnet route](/vpc/docs/routes#peering-subnet-routes)\nimported by the VPC Network Peering configuration. This insight\nshouldn't occur in public clusters.\n\n### Related topics\n\nFor more information, see\n[Control plane in private clusters](/kubernetes-engine/docs/concepts/private-cluster-concept#the_control_plane_in_private_clusters).\n\n### Recommendations\n\nGo to the GKE cluster details and verify VPC Network Peering.\nIf VPC Network Peering is deleted, create the GKE cluster again.\n\nGKE control plane to node connectivity blocked by ingress firewall on the node\n------------------------------------------------------------------------------\n\nThis insight indicates that the connection from the GKE control\nplane to the node is blocked by an ingress firewall on the node. This insight\nincludes the following information:\n\n- **GKE cluster:** The name of the GKE cluster.\n- **Control plane endpoint:** The IP address of the GKE control plane.\n- **Network:** The name of the network where the GKE cluster is configured.\n- **Blocking ingress firewall:** If the connectivity from the control plane to the node is blocked by an ingress firewall, it shows the name of this firewall; otherwise, this field is not displayed.\n- **Ports:** The ports on the GKE nodes that have the traffic blocked. For public clusters, the control plane communicates with GKE nodes on port 22. For private clusters, the control plane communicates with the GKE nodes on port 443 and port 10250.\n\nBy default, GKE creates\n[firewall rules](/kubernetes-engine/docs/concepts/firewall-rules#cluster-fws)\nto allow communication between the control plane and the GKE\nnodes in your project. This insight indicates that either these default firewall\nrules have been modified or removed, or that another firewall rule in your\nVPC network is shadowing the automatically created firewall rules.\n\n### Related topics\n\nFor more information, see\n[Automatically created firewall rules](/kubernetes-engine/docs/concepts/firewall-rules#cluster-fws)\nand [Firewall rules overview](/vpc/docs/firewalls).\n\n### Recommendations\n\n- If the automatically created firewall rule is deleted from your VPC network, re-create it.\n- If the automatically created firewall rule exists, then the blocking firewall rule has higher priority. Increase the priority on the automatically created firewall rule."]]