Backup for GKE pricing is based on three different dimensions:

• Backup management: this dimension is calculated at theBackupPlanlevel and is based on the number of Pods that are protected by theBackupPlan(the number of Pods contained in the most recentBackup for that plan).

• Backup storage: this dimension is calculated at theBackup level and isbased on the number of bytes stored for eachBackup over time.

• Network egress: this dimension is calculated at theBackup level and isbased on the number of bytes that's transferred across regions during thebackup operation. Note that these charges apply only when the source clusterand theBackupPlan are in two separate regions.

Pricing details may be found on the GKEpricing page.

Pricing for cross-project backups and restores

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

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

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

• restore_project: the project that contains the restore'starget cluster.

All three dimensions are billed in thebackup_project under theBackup for GKE line item.

Network data transfer charges

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

Adjust future billing

To stop any future billing for Backup for GKE, delete any existingBackupresources and then delete or disable anyBackupPlans.