k8s-backup

Automate Kubernetes backup and restore workflows using Velero.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/spigell/my-agents --skill k8s-backup-spigell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-backup
Source: https://github.com/spigell/my-agents/tree/main/agents/shared/src/tools/ask_kubernetes_expert/skills/k8s-backup
Command: npx skills add https://github.com/spigell/my-agents --skill k8s-backup-spigell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the operational problem of creating reliable Kubernetes backups and performing restores when you need to recover from incidents, migrate workloads, or protect production data.

Core Features & Use Cases

  • Create and manage Velero backups: Detect Velero availability, list available backup storage locations, and create backups for selected namespaces (optionally with selectors/exclusions).
  • Inspect and restore: List existing backups and schedules, monitor restore progress, and restore into the same or mapped namespaces for migration/disaster recovery.
  • Plan for DR workflows: Generate time-based DR backup names and restore them on a new cluster in a repeatable process (including restore variants like partial restores).

Quick Start

Use the k8s-backup skill to restore the namespace state from an existing Velero backup for a given application.

Frequently Asked Questions about k8s-backup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I back up and restore Kubernetes workloads using Velero?

Velero backup and restore workflows automate Kubernetes disaster recovery by detecting Velero availability, selecting storage locations, and creating scoped backups with TTL controls. You can restore into mapped namespaces for migration or recover workloads after incidents.

Can I migrate applications between Kubernetes clusters with Velero?

Yes, Velero enables Kubernetes application migration by restoring existing backups into mapped namespaces on a new cluster. You list available backups, select the target, and monitor restore progress to transfer workload state across clusters.

How do I create Kubernetes backups for specific namespaces with inclusion or exclusion filters?

Kubernetes namespace backups support optional inclusion and exclusion filters to scope workload protection. You select target namespaces, apply selectors or exclusions, set a backup TTL, and Velero creates the backup with those scope controls applied.

What's the best way to plan a disaster recovery backup workflow for Kubernetes?

Disaster recovery workflows use time-based Velero backup names to create repeatable processes for Kubernetes clusters. You generate DR backup names, create backups with TTL controls, and restore them on a new cluster, including partial restore variants when needed.

Do I need Velero installed before running Kubernetes backup operations?

Yes, Velero must be available in the cluster before creating Kubernetes backups. The workflow verifies Velero availability, lists backup storage locations, and uses Velero tools to create, inspect, and restore backups across selected namespaces.

Why does my Kubernetes restore with Velero not complete successfully?

Kubernetes restore issues often relate to Velero availability, backup storage location access, or namespace mapping configuration. You should verify Velero is installed, confirm the backup exists, and monitor restore progress through Velero tools to identify where completion stalls.