You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'll provide a way to integrate with Kopia's uploader and repository for filesystem based backup/restore.
Along with this work, we'll introduce the concept of "unified repository" to velero, and in the future, use it as the single target for all backup data.
We'll reuse the existing workflow and CR for restic repository, pod volume backup/restore but provide a switch for the code path, so user can choose to use restic(mostly existing code path) or kopia as the technology for the repository.
We'll provide a way to integrate with Kopia's uploader and repository for filesystem based backup/restore.
Along with this work, we'll introduce the concept of "unified repository" to velero, and in the future, use it as the single target for all backup data.
We'll reuse the existing workflow and CR for restic repository, pod volume backup/restore but provide a switch for the code path, so user can choose to use restic(mostly existing code path) or kopia as the technology for the repository.
An investigation has been done in v1.9: #4538 (comment)
The tech design (pending on approval): #4926
The text was updated successfully, but these errors were encountered: