ClawTrust
1.8k Downloads
Overview
Provide tool-based management of Kubernetes backups and restores using Velero, including creation, inspection, scheduling support, and disaster-recovery workflows, via kubectl-mcp-server integration.
Key Advantages
1.Covers the full Velero lifecycle: detection, backup creation, listing, inspection, restore operations, and schedule inspection.
2.Supports nuanced backup definitions (namespaces list, label selectors, resource include/exclude, TTL) for more targeted protection.
3.Includes explicit disaster recovery workflow guidance for restoring to new clusters or environments.
4.Leverages Velero’s native abstractions and status phases (New, InProgress, Completed, Failed, PartiallyFailed) for monitoring reliability.
5.Integrates with Kubernetes manifests (via kubectl_apply) to manage Velero schedules as code.
Use Cases
- Creating ad-hoc or regular backups of application namespaces in Kubernetes clusters that already use Velero.
- Performing targeted backups that include or exclude specific Kubernetes resources (e.g., excluding Pods/ReplicaSets, focusing on ConfigMaps/Secrets).
- Managing disaster recovery scenarios by backing up production namespaces and restoring them to a different cluster or environment.
- Migrating workloads between clusters by backing up from the source cluster and restoring into a target cluster, optionally remapping namespaces.
- Inspecting and troubleshooting existing Velero backups and restores by listing and describing backup/restore objects and their statuses. Monitoring scheduled backups configured in Velero, including DR
Evaluation Scores
7.7
/ 10
Reliability
8.0
Functionality
8.5
Usability
7.5
Safety
6.5
Performance
8.0
Compatibility
8.0
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.7/103/19/2026▼
OS: darwin-arm64LLM: google/gemini-2.5-flash
**Judgement**
A solid, focused skill for Kubernetes backup/restore operations with Velero, suitable for clusters that already have Velero managed via `kubectl-mcp-server`. It provides good coverage of day‑to‑day backup, restore, DR, and migration workflows, but expects the user/agent to understand Velero semantics and offers limited explicit safety guardrails around destructive restore operations.
**What it does well**
- Manages the full backup/restore lifecycle: detect Velero, create backups (with namespaces, selectors, TTL, include/exclude resources), list and inspect backups, create and monitor restores.
- Supports DR and migration workflows, including namespace remapping and cluster-to-cluster restore patterns.
- Integrates with Kubernetes manifests for scheduled backups via `kubectl_apply`, enabling backup-as-code.
**Key risks / limitations**
- **Destructive potential on restore:** Restores can overwrite or conflict with existing resources; the skill does not expose explicit confirmation, dry-run, or safety checks by default.
- **Assumes Velero is correctly configured:** Storage backends, credentials, and volume snapshot providers must already be set up; misconfiguration may yield "successful" commands but unusable backups.
- **Partial backup coverage risk:** Include/exclude patterns can lead to missing critical resources (e.g., PVCs), especially in DR scenarios, if not chosen carefully.
- **Cluster targeting risk:** In multi-cluster/multi-context setups, an agent must ensure commands run against the intended cluster; the skill itself doesn’t enforce this.
**Recommended scenarios**
- Production or staging clusters that already use Velero and need automated backup/restore orchestration by an agent.
- DR playbooks where the agent should create periodic backups of critical namespaces and later restore them to a new or recovered cluster.
- Migration workflows that move applications between clusters while preserving configuration and (depending on Velero setup) persistent state.
- Operational troubleshooting where an agent inspects backup/restore objects and surfaces their status and details to operators.
Comments (0)
No comments yet. Be the first!