# Idle GKE Cluster | Cloud Efficiency Hub Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/idle-gke-cluster GKE clusters created for testing, demos, proofs of concept, migrations or short-lived projects are often left running after the work ends. By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version GKE clusters created for testing, demos, proofs of concept, migrations or short-lived projects are often left running after the work ends. PointFive Research Cloud cost research at PointFive GCP service [GCP GKE](https://www.pointfive.co/efficiency-hub/cloud-services/gcp-gke) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0562 Type Idle or Unused Resource ## Explanation Why the waste happens and who it affects. Even with no customer workloads, every cluster pays the flat hourly cluster management fee, and a Standard cluster also pays for every node VM in its node pools, plus any persistent disks and load balancers the workloads created. Idle clusters are easy to miss because the cost is spread across Compute Engine, Kubernetes Engine and networking SKUs rather than showing up as one line item, and clusters without clear owner labels tend to be left alone. GKE's Idle GKE cluster recommender (google.container.DiagnosisRecommender) flags clusters that show no meaningful activity for 30 days and recommends deleting them. ## Billing model The pricing dimensions that drive this cost. Cluster management fee A flat per-cluster hourly fee for every GKE cluster in any mode; a monthly free tier credit per billing account covers one zonal Standard or Autopilot cluster Standard node pools Node VMs are billed at Compute Engine rates until the nodes are deleted, whether or not Pods are running Autopilot Pods Billed on Pod resource requests, so an empty Autopilot cluster mainly pays the management fee Attached resources Persistent disks and load balancers created by workloads bill separately and can outlive the cluster ## How to detect 5 checks to find it in your estate. - Review idle cluster insights and recommendations on the Clusters page Cost Optimization tab, with gcloud, or through the Recommender API (recommender google.container.DiagnosisRecommender, recommendation subtype CLUSTER\_IDLE) - CLUSTER\_IDLE\_NO\_RUNNING\_PODS: zero Pods in the Running state outside the kube-system and gmp-system namespaces over 30 days - CLUSTER\_IDLE\_NO\_NODES: zero nodes or zero node pools over 30 days, where the cluster pays only the management fee - CLUSTER\_IDLE\_LOW\_CPU\_UTILIZATION: CPU utilization averages under 7 percent in every hour over 30 days while the active Pod count stays unchanged - For clusters younger than 30 days, which GKE does not evaluate, check owner labels, creation purpose and last deployment time ## How to fix 5 ways to remove the waste. - Confirm with the owner that the cluster is not intentionally idle, for example as failover capacity, before acting on the recommendation - Export any manifests, configuration or data that must be kept, then delete the cluster - Delete Services of type LoadBalancer before deleting the cluster, since GKE might not remove every load balancer resource for clusters with many Services - After deletion, find and remove persistent disks that are no longer needed, because GKE retains persistent disk volumes during cluster deletion - For clusters that must stay but are rarely used, scale Standard node pools down or run the workloads in Autopilot, where empty clusters do not pay for idle nodes ## Documentation Vendor references for pricing and configuration. - [Identify idle GKE clusters docs.cloud.google.com](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/idle-clusters) - [Recommenders docs.cloud.google.com](https://docs.cloud.google.com/recommender/docs/recommenders) - [Deleting a cluster docs.cloud.google.com](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/deleting-a-cluster) - [Google Kubernetes Engine pricing cloud.google.com](https://cloud.google.com/kubernetes-engine/pricing) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - GCP GKE CER-0193 ### [Orphaned and Overprovisioned Resources in GKE Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-and-overprovisioned-resources-in-gke-clusters) As environments scale, GKE clusters tend to accumulate artifacts from ephemeral workloads, dev environments, or incomplete job execution. PVCs can continue to retain Persistent Disks, Services may continue to expose public IPs and... Compute - GCP GKE CER-0270 ### [Orphaned Kubernetes Resources in GKE](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-kubernetes-resources) In GKE environments, it is common for unused Kubernetes resources to accumulate over time. Examples include Persistent Volume Claims (PVCs) that retain provisioned Persistent Disks, or Services of type LoadBalancer that continue to front... Compute - GCP GKE CER-0287 ### [Spot-Only GKE Capacity Without Standard Fallback](https://www.pointfive.co/efficiency-hub/inefficiencies/spot-only-gke-capacity-without-standard-fallback) Workloads are constrained to run only on Spot-based capacity with no viable path to standard nodes when Spot capacity is reclaimed or unavailable. While Spot reduces unit cost, rigid dependence can create hidden costs by requiring standby... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.