Backup for GKE pricing

This document describes the pricing model and cost dimensions for Backup for GKE.

Backup for GKE helps you protect your GKE clusters and their workloads. By understanding how Backup for GKE calculates costs, you can effectively manage and optimize your backup expenses.

Your costs for Backup for GKE are determined by three dimensions:

• Backup management: calculated at the BackupPlan level. It's based on the number of non-system namespaces protected by your BackupPlan's most recent backup.
• Backup storage: calculated based on the number of bytes stored for each backup over time.
• Network egress: calculated based on bytes transferred across regions during backup operations. These charges apply only when your source cluster and BackupPlan are in different regions.

You can find full pricing details on the GKE pricing page.

Pricing for cross-project backups and restores

For any cross-project backup and restore scenarios, three projects are potentially involved:

• cluster_project: the project that contains the cluster that you want to back up.

• backup_project: the project where you want your backups to be stored.

• restore_project: the project that contains the restore's target cluster.

All three dimensions are billed in the backup_project under the Backup for GKE line item.

Network data transfer charges

Similar to single-project backup and restore operations, network data transfer charges apply for cross-region backup and restore operations. Additionally, there are network data transfer changes for Config backup during backup operations, between backup regions, and between restore regions when restoring a volume. These charges are listed under Compute Engine.

Adjust future billing

To stop any future billing for Backup for GKE, delete any existing Backup resources and then delete or disable any BackupPlans.