This page shows you how to potentially reduce your cluster operating costs byidentifying Google Kubernetes Engine (GKE) Standard clusters withunderutilized nodes that would benefit from a migration to GKEAutopilot.

Potential cost savings in Autopilot

In GKE Standard clusters, you're billed for theCompute Engine virtual machine (VM) infrastructure that backs each node,regardless of how efficiently your running workloadsuse the compute resources.Continually managing your resource usage using efficient resource consumption methods such asbin-packingis essential to run cost-efficient Standard clusters.

In Autopilot, you're billed for the compute resources, such as CPU ormemory, that your running workloads request. This billing model removes the needfor you to monitor and manage workload resource usage efficiency. For detailedpricing information,seeAutopilot mode pricing.

GKE monitors your running Standard clusters to detectnode underutilization and recommends migrating to Autopilot clustersif the migration would potentially reduce your operating costs. GKEprovides these recommendations throughRecommender,a service that provides insights and recommendations for using resources onGoogle Cloud.

Identify underutilized Standard clusters

GKE generates insights and recommendations that help you toidentify underutilized Standard clusters. To view these insights, usethe Google Cloud console, the gcloud CLI, or theRecommender API and specify the following parameters:

• Recommender type:google.container.DiagnosisInsight
• Subtype:CLUSTER_AUTOPILOT_OPTIMIZATION

For instructions, seeView insights and recommendations.

How GKE identifies clusters for potential Autopilot migration

GKE uses the following signals to determine whether aStandard mode cluster is underutilized. The cluster must satisfythe following signal for GKE to generate an insight:

Decide whether to migrate to Autopilot

Autopilot clusters shift node management responsibilities toGKE. Before you migrate your workloads to an Autopilotcluster, review the following resources to decide whether Autopilotfits your configurability and functionality needs:

• High-level comparison of cluster modes
• Detailed comparison of Autopilot and Standard
• Autopilot security overview
• About GKE Autopilot

In most production environments, we recommend Autopilot clusters.

Limitations

If recent metrics from a GKE Standard clusteraren't available, you might not see an insight for that cluster.

Act on the recommendation

If you see this recommendation, contact Cloud Customer Care for more informationabout how your environment might benefit from a migration to Autopilotclusters. Contact your account representative or seecontact Cloud Customer Care.

If you decide to migrate from Standard, check workload compatibilitywith Autopilot and prepare for a migration by following theguidance inPrepare to migrate to Autopilot form Standard.

What's next

• Optimize your usage of GKE with insights and recommendations.