Use numeric user for velero-restic-restore-helper #130
Conversation
(cherry picked from commit 00c1eb6) version bump; update restic branch/build;rebase log 1.6.0-rc.1 (cherry picked from commit 05bae5e) Fixed version tag for velero 1.6.0 (not rc1) (cherry picked from commit 8022187) Point back to konveyor-dev for restic (cherry picked from commit 8436504) Don't use builder from docker.io (cherry picked from commit 1f9a6f4)
(cherry picked from commit 56ef807)
Added support for restic volume checksum verification.
This adds another pod annotation ('backup.velero.io/verify-volumes')
which is used to identify which volumes on the pod should get the
'--verify' flag passed to restic when restoring.
Stdout and stderr are logged to the restic pod logs. The PodVolumeRestore
CRD has three new status fields: Errors, VerifyErrors, and ResticPod,
which contain the number of total errors reported, the number of verify
errors reported, and the name of the restic pod that ran the restore
(to allow for the user to look in the pod logs for more detailed output).
The Restore CRD has two new Status fields: PodVolumeRestoreErrors
and PodVolumeRestoreVerifyErrors, which contain a slice of ObjectReferences
listing which PodVolumeRestores contained errors or verify errors.
There is not yet support built into restore describe to see the restore fields
via the velero client. Also, the restic daemonset will need to have an env
variable set for POD_NAME.
(cherry picked from commit da2df66)
(cherry picked from commit 5a05c6b)
Signed-off-by: Scott Seago <sseago@redhat.com>
Signed-off-by: Scott Seago <sseago@redhat.com> (cherry picked from commit b845d23)
(cherry picked from commit fd5d85c)
(cherry picked from commit ccb545f) Update PR-BZ automation mapping (openshift#84) (cherry picked from commit aa2b019) Update PR-BZ automation (openshift#92) Co-authored-by: Rayford Johnson <rjohnson@redhat.com> (cherry picked from commit ecc563f) Add publish workflow (openshift#108) (cherry picked from commit f87b779)
updated version info
Signed-off-by: Norwin Schnyder <norwin.schnyder+github@gmail.com>
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
lifecycle/stale
|
@sseago: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/remove-lifecycle stale |
openshift-ci
bot
removed
the
lifecycle/stale
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci
bot
added
lifecycle/rotten
|
@sseago can this be closed? |
|
@weshayutin Looks like it can, yes. The current codebase has this change already, not only on the dev branch but also in the oadp release branches. |
Cherry-picked from cabd8e9