Stay organized with collections Save and categorize content based on your preferences.
GKE Dataplane V2 observability provides GKE Dataplane V2 metrics and insights into workloads on GKE clusters on Google Cloud. With GKE Dataplane V2 observability, starting with GKE versions 1.28 or later, you can:
GKE Dataplane V2 observability offers the following troubleshooting tools:
GKE Dataplane V2 metrics provide traffic flow information for the following:
Network policy enforcement: information about how GKE enforces Kubernetes Network Policies.
Note: Observability draws insights from Layer 3 and Layer 4 network data. This aligns with GKE's Network Policies, which also function at Layer 3 and Layer 4.You can use GKE Dataplane V2 metrics to monitor and troubleshoot Kubernetes workloads using the following tools:
When you enable Google Cloud Managed Service for Prometheus:
PodMonitoring resourceTo consume metrics with Google Cloud Managed Service for Prometheus and to be able to create a PodMonitoring resource, you must enable Google Cloud Managed Service for Prometheus on the cluster. If you don't enable Google Cloud Managed Service for Prometheus, GKE exposes the metrics endpoint but does not create a PodMonitoring resource.
When you enable GKE Dataplane V2 metrics for a cluster, Google Cloud Managed Service for Prometheus ingests the following GKE Dataplane V2 metrics:
GKE Dataplane V2 Metric Type Descriptionprometheus.googleapis.com/pod_flow_egress_flows_count/counter cumulative Total number of flows from a Pod. prometheus.googleapis.com/pod_flow_ingress_flows_count/counter cumulative Total number of flows to a Pod.
Enabling GKE Dataplane V2 metrics opens the metrics port on each Kubernetes node.
Additional metrics are also available, including from the open source observability platform Hubble. By default, Google Cloud Managed Service for Prometheus doesn't ingest these additional metrics but you can configure Google Cloud Managed Service for Prometheus to collect them. To collect these metrics, configure a PodMonitoring custom resource (CR).
The following table describes additional Hubble metrics:
Hubble metric Type Descriptionhubble_flows_processed_total cumulative Total number of flows processed. hubble_drop_total cumulative Total number of flows dropped. hubble_port_distribution_total cumulative Total number of flows processed aggregated by port number. hubble_tcp_flags_total cumulative Total number of flows processed with given TCP flags set. hubble_icmp_total cumulative Total number of ICMP flows processed. GKE Dataplane V2 observability tools
GKE Dataplane V2 observability provides a Managed Hubble solution with network observability and security insights for Kubernetes workloads deployed with GKE Dataplane V2.
When enabled, GKE Dataplane V2 observability deploys the following components to your cluster:
Hubble Relay: a service that collects network telemetry data about your Pods from each node.
Hubble CLI: a command-line interface tool providing live traffic information within the cluster.
You can deploy the following component after you enable GKE Dataplane V2 observability to your cluster:
GKE Dataplane V2 observability uses the following components and tools to collect metrics and provide insights into your network traffic:
GKE Dataplane V2: GKE Dataplane V2 metrics and observability use GKE Dataplane V2 datapath based on eBPF to collect metrics about traffic flows and network policy enforcement for a Pod based on a given workload.
Google Cloud Managed Service for Prometheus: GKE Dataplane V2 metrics configures the Google Cloud Managed Service for Prometheus agent to ingest aggregated metrics to Google Cloud Managed Service for Prometheus, a scalable monitoring solution that can ingest and store large amounts of data that also lets you build on the Google Cloud Observability.
Hubble: GKE Dataplane V2 observability uses Hubble, an open source observability project. Hubble enables network observability and security insights for Kubernetes workloads deployed with an eBPF Dataplane.
Hubble flow events occur when:
A network connection is first established
A TCP flag is first seen, which indicates the state of the TCP connection
A packet is transmitted after at least five seconds have passed since the last flow event
Hubble metrics: counts the number of flow events in a Kubernetes cluster that you can use to identify which Pods are communicating with each other.
Note: Hubble flow metrics don't count the amount of data or number of packets transmitted.Enabling metrics and observability: You can enable GKE Dataplane V2 and observability independent of each other. To enable Network topology visualization in open source Hubble UI feature, you must enable Network inspection.
Autopilot clusters:
Metrics are enabled by default
Observability tools are disabled by default
You must create the ClusterPodMonitoring resource to gather metrics in the Google Cloud Managed Service for Prometheus
Standard clusters:
Metrics are disabled by default
Observability tools are disabled by default
If you have Google Cloud Managed Service for Prometheus enabled, a PodMonitoring resource is created automatically
A PodMonitoring resource is marked as ensure exists. You can stop sending metrics to Google Cloud Managed Service for Prometheus by editing the PodMonitoring resource to disable all metrics
GKE Dataplane V2 observability components expose the following two observability endpoints:
Metrics endpoint: an HTTP endpoint that exposes traffic metrics in Prometheus format. The anetd Pod exposes the metrics endpoint on each cluster node on port 9965.
Flows port: a gRPC endpoint. The hubble-relay Pod exposes the flows port endpoint as a Kubernetes ClusterIP Service on port 443. The hubble-relay Pod is the backend for the Kubernetes ClusterIP Service and all requests to the Kubernetes ClusterIP Service are forwarded to the hubble-relay Pod. You can access the flow port using Hubble CLI or the Hubble UI.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-11 UTC."],[],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4