Shubham Pampattiwar
f8c23ef4e0
Adds ARCHITECTURE.md as a high-level, discoverable entry point to Velero's architecture, goals, and use cases that links to velero.io and the design/ directory instead of duplicating content. Expands ROADMAP.md from a single wiki link (which pointed at the stale vmware-tanzu path) into a short description of how the roadmap is maintained, and repoints the wiki link to velero-io. Links ARCHITECTURE.md from the README so it is easy to find. These docs address incubation-review feedback that Velero's goals, architecture, and roadmap process were scattered across the website. Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>
1.6 KiB
Velero Architecture
This is a high-level entry point to Velero's architecture. It links to the authoritative material rather than duplicating it, so the details stay in one place and do not drift.
How Velero works
Velero runs a server (a set of controllers) in your cluster and a command-line client that runs locally. Backups and restores are driven by Kubernetes custom resources and reconciled by the server. Volume data is moved by the built-in file-system backup and by the data mover, and object and volume snapshot operations are handled through provider plugins.
For the full component overview, the backup and restore flows, and the object storage and snapshot model, see:
Goals
Velero gives you tools to back up and restore your Kubernetes cluster resources and persistent volumes, on public cloud or on-premises. The primary use cases are:
- Take backups of your cluster and restore in case of loss.
- Migrate cluster resources to other clusters.
- Replicate your production cluster to development and testing clusters.
Design proposals
Accepted and proposed designs live in the design/ directory. New
designs follow design/_template.md and are reviewed
through pull requests and the community meetings. Implemented designs are
archived under design/Implemented/.