Epic Goal

• The goal for this epic to track the work required to allow users to either use restic or kopia uploader type.
• Why is this important?  Kopia offers several advantages over restic, see the upstream design for details. Kopia support has been G.A since velero v1.10

• [Upstream Design|(https://github.com/vmware-tanzu/velero/blob/main/design/unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md]
• Downstream Design

Scenarios

1. Same as current restic workflows

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

1. Velero

Open questions::

1. TBD 

Done Checklist

• [ x ] CI - CI is running, tests are automated and merged.

• [ ] Release Enablement <link to Feature Enablement Presentation>

• [ x ] DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>

• [ ] DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>

• [ ] DEV - Downstream build attached to advisory: <link to errata>

• [ ] QE - Test plans in Polarion: <link or reference to Polarion>.
• [ ] QE - 1 - Regression tests, All the existing tests should pass
• [ ] QE - Automated tests merged: <link or reference to automated tests>

• [ ] DOC - Downstream documentation merged: <link to meaningful PR>