// the find
backube/volsync
Asynchronous data replication for Kubernetes volumes
VolSync is a Kubernetes operator that replicates persistent volumes between clusters using rsync, rclone, or restic as the underlying transport. It targets platform engineers who need async PV replication or backup without being locked into a specific storage vendor's snapshot mechanism. Still self-labelled alpha.
The mover abstraction is genuinely well-designed — rsync, rclone, restic, and syncthing each live in their own package implementing a common interface, so adding a new backend doesn't touch the controller logic. Using battle-tested data tools (rsync/restic/rclone) as movers rather than reinventing transfer means the actual data movement is solid. The CSI-agnostic approach means it works with any storage class that supports volume snapshots, not just one vendor's product. The API types are dual-licensed Apache 2.0 specifically so other operators can import and use the CRDs without the AGPL infecting their code — that's a thoughtful call.
Still alpha after what looks like several years of active development; that badge is doing a lot of work and will make anyone running production workloads nervous. The AGPL license on the operator itself will block adoption in any shop with a policy against copyleft in infrastructure tooling. Under 1000 stars for a project solving a real pain point suggests the operator ecosystem hasn't widely adopted it, which means fewer eyes on edge cases in the data path where bugs matter most. Syncthing support appears to be a half-finished experiment — it's a continuous-sync tool bolted onto a batch-replication API, and the mismatch in mental models will bite operators who don't read carefully.