Daniel Jiang

Supporting recovery or dataupload is a valid requirement but in short term I don't think we have bandwidth to handle that.

This issue was opened when we observe the issue that the jobs are not reserved as configured. The enhancement proposed in this issue is valid but we may first focus...

Currently, there are information related to the details of maintenance printed in the job log. So to this issue is essentially tracking a UX improvement. Let's leave it in the...

Move out of v1.15 b/c we cannot reproduce this issue and pending for more info from the author.

Do you have to use restic? In later versions of velero kopia is more actively maintained and supported.

@limityu If it's reproduced with kopia, I'd suggest we fix it in kopia path. Please reproduce the issue using kopia, and collect the debug bundle via `velero debug`, and attach...

@shubham-pampattiwar @sseago @kaovilai LGTM, but shall we hold it after the branch is cut for v1.15? Unfortunately we see issues in the internal pipeline and still fixing it.

@soumyapattnaik After reading the descriptioin I'm confused: > In the finalizing phase today, we do a get on volumesnapshot, if it fails due to some transient failures like TLS handshake...

@soumyapattnaik After checking the code, this is a valid issue, the root cause is that the `Execute` of CSI BIAv2 is executed again in `FinalizeBackup` and the code in the...

Let's make sure we skip checking the volumeHandler in "finalizing". But general speaking if the api-server is flaky we can't guarantee the backup is still successful. Therefore, we will not...