cdchris12
commented
3 years ago Seems like this is entirely resolved by #57 . Would love to see that rolled out in a release we could use with k8up 😄
Closed cdchris12 closed 3 years ago
cdchris12
commented
3 years ago Seems like this is entirely resolved by #57 . Would love to see that rolled out in a release we could use with k8up 😄
srueg
commented
3 years ago
Summary
As "a person who uses k8up which consumes wrestic"\ I want "the latest version of restic to be used"\ So that "prunes can be completed substantially faster and safer"
Context
Wrestic currently uses restic version 0.9.5 , which is now 2 years old. Restic recently released version 0.12.0, which contains numerous improvements. Most notably, this version brings substantial improvements to the prune process, allowing for prunes to use significantly less RAM, network IO, and file storage space while also performing no operations on the repo if they are canceled before completely finishing operations on the remote restic repo.
Out of Scope
Further links
Acceptance criteria
Given "k8up starts a backup/restore/prune pod"\ When "a backup/restore/prune operation is requested"\ Then "the resulting wrestic pod will be running restic version 0.12.0"
Implementation Ideas
It seems like this could be accomplished simply by updating the version of restic pointed to in the Dockerfile.