This page shows you how to potentially reduce your cluster operating costs by
identifying Google Kubernetes Engine (GKE) Standard clusters with
underutilized nodes that would benefit from a migration to GKE
Autopilot.

## Potential cost savings in Autopilot

In GKE Standard clusters, you're billed for the
Compute Engine virtual machine (VM) infrastructure that backs each node,
regardless of how efficiently your running workloads *use* the compute resources.
Continually managing your resource usage using efficient resource consumption methods such as *bin-packing*
is essential to run cost-efficient Standard clusters.

In Autopilot, you're billed for the compute resources, such as CPU or
memory, that your running workloads request. This billing model removes the need
for you to monitor and manage workload resource usage efficiency. For detailed
pricing information,
see [Autopilot mode pricing](https://cloud.google.com/kubernetes-engine/pricing#autopilot-mode).

GKE monitors your running Standard clusters to detect
node underutilization and recommends migrating to Autopilot clusters
if the migration would potentially reduce your operating costs. GKE
provides these recommendations through [Recommender](https://docs.cloud.google.com/recommender/docs/overview),
a service that provides insights and recommendations for using resources on
Google Cloud.

## Identify underutilized Standard clusters

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

- **Recommender type:** `google.container.DiagnosisInsight`
- **Subtype** : `CLUSTER_AUTOPILOT_OPTIMIZATION`

For instructions, see
[View insights and recommendations](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/optimize-with-recommenders.md.txt#view-insights-recs).

## How GKE identifies clusters for potential Autopilot migration

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

| Signal | Description | Threshold |
|---|---|---|
| CPU bin-packing score | The amount of node CPU requested by running workloads as a percentage of the total available CPU on the node. | \<55% |

### Decide whether to migrate to Autopilot

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

- [High-level comparison of cluster modes](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/choose-cluster-mode.md.txt)
- [Detailed comparison of Autopilot and Standard](https://docs.cloud.google.com/kubernetes-engine/docs/resources/autopilot-standard-feature-comparison.md.txt)
- [Autopilot security overview](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/autopilot-security.md.txt)
- [About GKE Autopilot](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview.md.txt)

In most production environments, we recommend Autopilot clusters.

### Limitations

If recent metrics from a GKE Standard cluster
aren'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 information
about how your environment might benefit from a migration to Autopilot
clusters. Contact your account representative or see
[contact Cloud Customer Care](https://cloud.google.com/contact).

If you decide to migrate from Standard, check workload compatibility
with Autopilot and prepare for a migration by following the
guidance in
[Prepare to migrate to Autopilot form Standard](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/prepare-migrate-cluster-mode.md.txt).

## What's next

- [Optimize your usage of GKE with insights and recommendations](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/optimize-with-recommenders.md.txt).