Learn Velero - Ecosystem, Alternatives & Final Reflection

#Introduction

This is the last episode. You've completed 22 episodes: from setting up the environment, installing Velero, backup/restore, scheduling, hooks, migration, DR, security, troubleshooting, to the roadmap. Episode 22 closes with three things: positioning Velero among other tools, summarizing the whole journey, and — most useful of all — a production checklist you can use right away.

The best skill of an engineer isn't memorizing commands, but choosing the right tool for the right problem. You now know what Velero does very well, and what should be handled by other tools.

#Comparison with Alternatives

+----------------+--------------+---------------------------+-----------------------------------+
| Tool           | Type         | Main strength             | When to use                       |
+----------------+--------------+---------------------------+-----------------------------------+
| Velero         | General BaaS | resource + volume backup, | general backup, cross-cluster     |
|                | open source  | cross-cluster migration   | migration, no vendor lock-in      |
| Kasten K10     | Enterprise   | UI, policy, compliance,   | need an enterprise dashboard,     |
| (Veeam)        |              | ecosystem integration     | managed policies                  |
| Stash          | Script-based | script-based backup       | workload-specific with custom     |
| (AppsCode)     |              | (restic), operator        | backup scripts                    |
| CloudNativePG/ | DB-specific  | PostgreSQL backup inside  | PostgreSQL database workloads     |
| PGO            |              | K8s (PITR, WAL archiving) | that need point-in-time           |
| etcd backup    | Cluster state| cluster state snapshot    | recovering cluster state, not     |
|                |              |                           | application data                  |
+----------------+--------------+---------------------------+-----------------------------------+

#When to Choose Velero

• General K8s backup and cross-cluster migration → Velero is the most balanced choice: open source, mature, portable.
• Need an enterprise UI, layered policies, and vendor support → Kasten K10 is worth evaluating (built on a similar backup concept).
• Stateful databases (especially PostgreSQL) requiring point-in-time recovery and WAL archiving → CloudNativePG/PGO or a DB-native tool like pgbackrest (see the learn-pgbackrest series).
• Cluster state (e.g. recovering the control plane) → etcd snapshot, not Velero.

Importantly, these tools complement each other, not replace one another. Many productions use Velero for general backup and CloudNativePG for Postgres backup — both at once.

#Journey Recap

Phase 1 (episodes 0-2): environment, history, and architecture — the BSL/VSL foundation and the role of plugins.

Phase 2 (episodes 3-7): core operations — install, first backup, selective restore, scheduling + TTL, labels/selectors/annotations.

Phase 3 (episodes 8-12): data and DR — cloud snapshot vs kopia, consistency hooks, restore workflow + namespace mapping, cross-cluster migration, and a DR plan with RPO/RTO and drills.

Phase 4 (episodes 13-16): security and resilience — credentials + RBAC, encryption, backup policies + compliance, troubleshooting.

Phase 5 (episodes 17-20): advanced — Velero 1.18, plugin ecosystem, CSI snapshot & cross-provider, performance.

Phase 6 (episodes 21-22): ecosystem — roadmap/community and the final reflection.

#Production Checklist

Before we end, here's the checklist that must be satisfied in production:

• BSL/VSL shows Available, correct region, secure credentials (IRSA/Workload Identity where possible).
• Schedule + TTL matches the RPO; tiered retention (hourly/daily/weekly/monthly) when needed.
• Pre/post hooks for stateful workloads (PostgreSQL/MySQL) so backups are consistent.
• node-agent (kopia) active for PVCs; cloud snapshots for large workloads in the same region.
• Encryption: SSE/KMS on the bucket, encrypted snapshots, HTTPS endpoints.
• RBAC: access to the velero namespace restricted; credentials never committed.
• Monitoring: failed backups detected automatically (server logs, events, reports).
• Regular DR drills: restore to a new cluster tested, actual duration recorded vs RTO.
• restic → kopia migration completed before Velero 1.19.
• Upgrade testing: restore test in staging before upgrading Velero/K8s.

#Official Learning Resources

• Docs: velero.io/docs — getting started, architecture, troubleshooting.
• GitHub: github.com/velero-io/velero — compatibility matrix, release notes, issues.
• Slack: Kubernetes Slack, #velero channel.
• CNCF: the Velero project page.
• Follow-up series: learn-kubernetes (basics), learn-pgbackrest (Postgres backup), learn-vault (secret management), learn-gitops-argocd (deployment/DR), and learn-restic/learn-borg-backup (file backup).

#Closing

Key takeaways:

• Velero wins with the combination: open source, general-purpose, and portable — for cross-cluster migration it's nearly unmatched.
• Kasten for enterprise, Stash for scripts, CloudNativePG for Postgres, etcd for cluster state — choose by problem.
• Recap of 6 phases: foundation → operations → data & DR → security → advanced → ecosystem.
• Production checklist: 10 items to satisfy before you sleep well.
• Keep learning from the official docs, the community, and the supporting series.

Thank you for completing Learning Velero! You now have the knowledge and skills to build backup, restore, migration, and disaster recovery systems you can truly rely on in Kubernetes. One final message: don't stop at reading — run a DR drill next week. A backup tested many times is far more valuable than a backup remembered once. Happy building!