Menu
Workflows for configuring Backup for GKE and disaster recovery.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Systematically diagnose GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads. Identifies preemption events, maintenance interruptions, bad host VMs, unhealthy pods, and coordinator worker failures.
Diagnose and predict node disruption during Compute Engine host maintenance for GPU and TPU workloads.
Diagnose and prevent `vbar_control_agent` segfaults and OOMs caused by race conditions during TPU device resets and frequent metrics collection (e.g. every 3s). Use when TPU slice initialization fails or `vbar_control_agent` crashes on TPU v6e nodes.
Verifies if a GKE or Kubernetes cluster is unused (no active compute, external exposure, or persistent data) before allowing deletion. Evaluates external exposure (LoadBalancer Service, Ingress, Gateway, MultiClusterIngress), persistent data (Bound PVC), and active compute (Running/Pending Pods in user namespaces) with low-overhead queries and fail-close timeouts.
Monitor and manage GKE TPU Dynamic Slices custom resources. Use when checking slice lifecycle states, troubleshooting failed slice creations (e.g. SliceCreationFailed, FAILED), running single or multi-slice workloads, or safely deleting/disabling slices.
Monitor and troubleshoot GKE TPU workloads using GKE system metrics and PromQL.
| name | gke-backup-dr |
| description | Workflows for configuring Backup for GKE and disaster recovery. |
This skill provides workflows for protecting your stateful workloads on GKE using Backup for GKE.
Backup for GKE must be enabled on the cluster level.
Command:
gcloud container clusters update <cluster-name> \
--enable-gke-backup \
--region <region>
A Backup Plan defines what to back up, when, and for how long.
Command to create a backup plan:
gcloud container backup-restore backup-plans create <plan-name> \
--cluster=<cluster-name> \
--region=<region> \
--retention-days=<days> \
--cron-schedule="<cron-expression>" \
--all-namespaces
[!NOTE] You can replace
--all-namespaceswith--included-namespaces=<namespace1>,<namespace2>to back up specific namespaces instead of all of them.
Encryption Note: You can specify a Customer-Managed Encryption Key (CMEK) to encrypt backups. Add --backup-encryption-key=<key-resource-name> to the create command.
Trigger a backup immediately outside the schedule.
Command:
gcloud container backup-restore backups create <backup-name> \
--backup-plan=<plan-name> \
--region=<region>
Restore a workload or cluster from a backup.
Command to create a restore plan:
gcloud container backup-restore restore-plans create <restore-plan-name> \
--cluster=<target-cluster-name> \
--region=<region> \
--backup-plan=<source-backup-plan-name> \
--cluster-resource-conflict-policy=USE_EXISTING_VERSION \
--namespaced-resource-restore-mode=FAIL_ON_CONFLICT
Execute the restore:
gcloud container backup-restore restores create <restore-name> \
--restore-plan=<restore-plan-name> \
--backup=<backup-name> \
--region=<region>