Stay organized with collections
Save and categorize content based on your preferences.
Autopilot
Standard
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Backup for GKE pricing\n\nAutopilot Standard\n\n*** ** * ** ***\n\nBackup for GKE pricing is based on three different dimensions:\n\n- **Backup management** : this dimension is calculated at the `BackupPlan`\n level and is based on the number of Pods that are protected by the `BackupPlan`\n (the number of Pods contained in the most recent `Backup` for that plan).\n\n- **Backup storage** : this dimension is calculated at the `Backup` level and is\n based on the number of bytes stored for each `Backup` over time.\n\n- **Network egress** : this dimension is calculated at the `Backup` level and is\n based on the number of bytes that's transferred across regions during the\n backup operation. Note that these charges apply only when the source cluster\n and the `BackupPlan` are in two separate regions.\n\nPricing details may be found on the GKE [pricing page](/kubernetes-engine/pricing#backup-for-gke).\n\nPricing for cross-project backups and restores\n----------------------------------------------\n\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nFor any cross-project backup and restore scenarios, three projects are\npotentially involved:\n\n- **`cluster_project`**: the project that contains the cluster that you\n want to back up.\n\n- **`backup_project`**: the project where you want your backups to be\n stored.\n\n- **`restore_project`**: the project that contains the restore's\n target cluster.\n\nAll three dimensions are billed in the `backup_project` under the\nBackup for GKE line item.\n\n### Network data transfer charges\n\nSimilar to single-project backup and restore operations, network data transfer\ncharges apply for cross-region backup and restore operations. Additionally,\nthere are network data transfer changes for `Config backup` during\nbackup operations, between backup regions, and between restore regions when\nrestoring a volume. These charges are listed under Compute Engine.\n\nAdjust future billing\n---------------------\n\nTo stop any future billing for Backup for GKE, delete any existing `Backup`\nresources and then delete or disable any `BackupPlans`."]]
