Velero

Velero is a Kubernetes backup and disaster recovery CLI that installs and drives in-cluster controllers for backing up, restoring, and migrating cluster resources and persistent volume data. It covers the operational path from initial install and storage configuration to scheduled backups, restore execution, and repository maintenance.

• Install Velero into a cluster, attach the right storage plugins, and configure object storage, snapshot locations, node agents, and maintenance settings from the terminal.
• Create on-demand or scheduled backups with namespace, resource, and label filters, choose snapshot or file-system backup behavior, and protect cluster state before upgrades, migrations, or incident response work.
• Inspect backup, restore, storage location, plugin, and backup repository objects, fetch operation logs, and run restores with namespace remapping or existing-resource update policies.

• Flag-driven commands, kubeconfig and namespace selection, wait flags, and create/get flows make it workable in scripted backup and restore loops once cluster access already exists.
• Key create, get, install, and location queries can emit JSON or YAML, but some important follow-up work still happens through plain-text describe output and streamed logs.
• Best when a skill already knows the target cluster, storage backend, and safe restore scope, because the CLI mostly submits Kubernetes custom resources and then waits for asynchronous controllers to finish the real work.

• The CLI is only one part of the system: useful work depends on a running Velero deployment plus configured object storage or snapshot plugins and the right Kubernetes credentials.
• Backup and restore actions are high impact, and file-system backup or node-agent setups can require privileged access and platform-specific tuning.