Update Velero to support restic restores of pods managed by DeploymentConfigs

[dymurray]

There has been a longstanding upstream issue with taking restic backups/restores of volumes which are mounted via pods that are owned by DeploymentConfigs. What ends up happening is at restore time, Velero restores the pod that mounts the volume and the DeploymentConfig which manages the pod.

This causes problems as the deploymentconfig adopts the restored pod, and redeploys a new version while terminating the old one. This is a problem because the restored pod contains the initContainer which waits for the restic restore to complete. Without this pod running with the initContainer, the restic restore process fails.

Related issues:
vmware-tanzu/velero#2073
vmware-tanzu/velero#1981

If we decide that we cannot change the upstream code to support this, then we will want to at a minimum document the process of creating 2 restores (first restore just pods+pvcs, second restore everything else) to workaround this.

[dymurray]

Documented workaround: https:/openshift/oadp-operator/blob/master/TROUBLESHOOTING.md#known-issue-with-backuprestore-of-deploymentconfigs-using-restic

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.