Stash was an inspiration for K8up. Unlike Stash, K8up is non-intrusive and doesn't add additional containers to Pods. It runs as k8s jobs besides the application Pods.
K8up currently is optimized for PVs and will probably be able to backup objects in the future. It's not meant for cluster disaster recovery or full-cluster backup. (Deployment artefacts should anyways come from GitOps)
SomaticPirate, Stash can backup individual workloads, PV/PVC or any application (Databases or custom including K8s cluster) with the most recent release.
I actually have a cluster that I need to tear down and do disaster recovery practice on, but didn't know how, so I'm still paying for the "important data" that I generated on it.
How does this compare?
[1] https://github.com/miracle2k/k8s-snapshots
* K8up doesn't do snapshots but file-based backups supporting any RWX storage and to some extend RWO (still to be improved)
* K8up can do pre-backup tasks like dumping a database to have application consistent backups
* K8up has a great amount of monitoring backed in for providing a good overview via Prometheus if the backups really work
* K8up can send webhooks about backups available to allow integrations into third party control panels. F.e. Lagoon[1] uses it
[1] https://github.com/amazeeio/lagoon
Does that mean I could use the SFTP transport of restic and send my K8up generated backups to any old SFTP server ?
Disclaimer: My company, AppsCode is the primary developer behind Stash.
I will use it tonight, thank you friend!