[[["容易理解","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,["# Use case: Troubleshoot GKE connectivity\n=======================================\n\nIn this use case, you're a network administrator supporting a network that\nincludes several GKE namespaces. You've been alerted of a latency\nproblem and have been told that your organization's mobile application is\nintermittently\nslow and timing out. You know that a number of different users are affected, and\nthat there have been no recent application deployments. The issue is likely\nrelated to a specific GKE cluster.\n\nThe following use case demonstrates how Network Topology can help you\nquickly troubleshoot and investigate issues in your GKE\ndeployment.\n\nTopology details\n----------------\n\nThe deployment spans three Google Cloud regions (`us-central1`,\n`europe-west1`, and `asia-east1`). All external client requests are served by\nthe three clusters within the three regions with multiple namespaces. Client requests\nthat come from one of three business regions (Americas,\nEMEA, and APAC) are served by application instances in the closest\nGoogle Cloud region.\n\nThe following topology shows the top-level hierarchy for the deployment:\n[](/static/network-intelligence-center/docs/network-topology/images/use-cases/gke-auditing-topology.png) Network Topology GKE view example topology (click to enlarge)\n\nNetwork latency\n---------------\n\nIn this scenario, assume that you have a GKE cluster named\nonline-boutique. You check the latency between external clients and the\nGKE cluster to see if the latency between them has changed. You\ndiscover that it has changed and decide to further\ninvestigate the cluster's nodes.\n\n1. You filter the topology to show only the traffic for your cluster\n `online-boutique`.\n\n In the **Filter** section, you can add a filter to select nodes and its\n peers. This section is available only for metric views and not for the\n insights views. Click **Add filter** and select the type of node and the\n node.\n\n After you apply the filter, Network Topology shows only the connections\n related to the cluster, as shown in the following example.\n2. Starting with the external clients in Americas, you click the traffic\n metrics between the Americas business region and the GKE cluster.\n Network Topology shows charts in the details pane. The information includes\n ingress and egress traffic between your selected entity and the connected\n entity. For example, Network Topology provides the latest values for\n queries per second (QPS) and the HTTP request latency.\n In the request latency chart, you see values for the 50th, 95th, and 99th\n percentiles. In this example, assume that all of the latency values are\n higher than you expected.\n\n3. To expand the time series charts to 6 weeks, at the top of the details\n pane, you select **6 weeks**.\n\n You see a significant jump that happened about two hours ago, roughly when\n the first issues were reported. You're confident that the issue is related\n to increased latency with a GKE Pod.\n | **Note:** Traffic details from external entities are only available till the GKE cluster level. Network Topology does not show the traffic to the nodes within a GKE cluster.\n4. Having a high-level view of the issue, you investigate the GKE nodes\n further. For more information about troubleshooting GKE\n nodes, see [Troubleshooting GKE connectivity issues](/kubernetes-engine/docs/troubleshooting#ConnectivityIssues).\n\nWhat's next\n-----------\n\n- [Monitor your networking configuration with Network Topology](/network-intelligence-center/docs/network-topology/how-to/audit-troubleshoot-networking-issues)\n- [Use case: Audit network performance](/network-intelligence-center/docs/network-topology/concepts/auditing-network-performance)\n- [Troubleshoot Network Topology](/network-intelligence-center/docs/network-topology/support/troubleshooting)\n- [Cloud Interconnect quotas and limits](/network-connectivity/docs/interconnect/quotas)\n- [Cloud VPN quotas and limits](/network-connectivity/docs/vpn/quotas)"]]
