I built a small Kubernetes operator that automates PV snapshots for StatefulSets using custom resources for scheduling and retention. It's at v0.0.1-alpha and very experimental. The idea was to explore a pattern where backup configuration lives as CRDs alongside StatefulSet definitions, rather than using external tooling. Obviously Velero is more mature and feature-complete for production backup/DR needs. This is narrower in scope - just StatefulSet snapshots via the K8s VolumeSnapshot API. Would love feedback on whether this approach makes sense for any real-world scenarios, or if it's solving a problem that doesn't really exist.