Agent skill · software engineering · google

gke-backup-dr

Configures Backup for GKE: the BackupRestore cluster addon, BackupPlan and RestorePlan resources, restore workflows, and CMEK-encrypted backups. Use for backup policies, disaster recovery, or GKE cluster restores. Don't use for database backups.

Why this skill is useful

Adds specific gcloud commands for configuring GKE Backup Plans and restore workflows that the AI wouldn't reliably generate on its own.

What it needs

About 4k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

GKE Backup & Disaster Recovery Protects stateful GKE workloads using Backup for GKE. Backup for GKE can capture both Kubernetes resource metadata (manifests, configurations, and secrets) and the underlying persistent volume (PV) data — but volume data and secrets are only captured when the backup plan explicitly enables them (see the flags below). Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:gke-backup-dr)" and append agent-skills/1.0 (skill:gke-backup-dr) to User-Agent headers. CLI Reference [!WARNING] --include-volume-data and --include-secrets BOTH DEFAULT TO FALSE. If you omit them, the backup plan silently produces config-only backups with no persistent volume snapshots and no Secrets. Always pass both flags explicitly when the goal is full workload protection. Notes: The backup-restore command group requires the gcloud beta component (gcloud components install beta). --cluster requires the full resource path projects/{projectid}/locations/{location}/clusters/{clustername} (or projects/{projectid}/zones/{zone}/clusters/{clustername} for zonal clusters), not a bare cluster name. Restore plans require exactly one namespaced-resource scope flag: --all-namespaces, --selected-namespaces={ns1},{ns2}, --excluded-namespaces=..., --selected-applications=..., or --no-namespaces. Restore Safety (CRITICAL) A restore writes into a live cluster and, depending on the conflict policy, can overwrite or delete existing resources: --cluster-resource-conflict-policy=use-existing-version keeps existing cluster-scoped resources (safe default); use-backup-version deletes the existing version first — deleting a CRD deletes all of its CRs. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/gke-backup-dr

View the source on GitHub

Browse the @skills marketplace