Backup for GKE pricing

Backup for GKE pricing is based on three different dimensions:

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

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

• Network egress: this dimension is calculated at the Backup level and is based on the number of bytes that's transferred across regions during the backup operation. Note that these charges apply only when the source cluster and the BackupPlan are in two separate regions.

Pricing details may be found 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.