RFC: Upstream to redhat-cop

[hairmare]

Hi world + team

It feels like the time has come to sort out the future governance and direction of this humble following the book implementation of low-level etcd snapshotting.

The contributions this solution attracted in the past (e.g. this) as well as features requests like S3 (better evidenced in the @stianfro fork) make me think that we should take this effort further to ensure it can be used to it's full potential.

I'd propose that we:

• Ask redhat-cop if they would like to provide a community space to host this solution
• If we get the go ahead, merge the helm repo into this
• and move the solution to @redhat-cop
• commit to stewarding the solution at it's new home + engaging additional collaborators

In it's new home we would have a venue to open up the discussion about S3 and other features at large. Me personally, i'm throwing my hat in the ring towards us just supporting a high-level tool like rclone properly to isolate us even further from the issue.

We initially started this repo wanting to 1-1 implement what the docs recommend. Is migrating this use-case to a more proactive approach worth doing compared to what has become available in the meantime with ie. Velero? I'm not the one to decide, so I'm posting this since I'd love some external input!

[tongpu]

Adding rclone to support a broad set of destination stores would be a nice addition.

Do you know anyone within redhat-cop?