Design: Consider a smaller release w/ kopia TP and native dm TP

Context:

• This may change our roadmap a bit and further delay releasing OADP that supports non-admins ability to backup and restore.
• Upstream Velero has support for kopia
• Upstream Velero will release a native datamover w/ kopia in velero 1.12
• It may make sense to get both features in OADP as tech preview asap.
• If we do NOT bring both features in ASAP what are the consequences?

Requirements

• Discuss the trade off

https://github.com/vmware-tanzu/velero/wiki/1.12-Roadmap

We could consider a short 1.3.0 cycle that includes tech-preview features.

• velero 1.12 ( release date planned for Aug 23rd )
• kopia vs. restic file backup
• native datamover via velero w/ kopia
• Ensure OADP GA datamover continues to work w/ velero 1.12

• bug fixes

Notes:

• Do we keep datamovers completely separate?
  • Alternative is to integrate OADP dm into upstream velero 1.12 api

Start with the linked Velero 1.12 roadmap and the issue’s context about kopia, restic file backup, and the native datamover. Compare the trade-offs of a short 1.3.0 tech-preview cycle, keeping datamovers separate, or integrating with the Velero 1.12 API. Done means documenting a clear recommendation and its consequences for OADP’s GA datamover and non-admin backup and restore.