I executed the native datamover backup and restore on same namespace after successful backup and restore via Kopia. I noticed velero is restoring restore-wait init container even though it's not required in this case.

Version-Release number of selected component (if applicable):
Velero-1.12

Steps to Reproduce:

1. Deploy an application consisting PVC's

2. Trigger a file system backup

3. Delete app namepace

4. Execute Restore

5. Now backup the same namespace via native datamover or CSI

6. Delete app namespace

7. Execute restore

Actual results:

Application pod has the init container added in it.

$ oc get pod -n ocp-mysql
 initContainers:
    - args:
      - 926e0ef5-5038-49d4-8f63-259acee86e42
      command:
      - /velero-restore-helper
      env:
      - name: POD_NAMESPACE
        valueFrom:
          fieldRef:
            apiVersion: v1
            fieldPath: metadata.namespace
      - name: POD_NAME
        valueFrom:
          fieldRef:
            apiVersion: v1
            fieldPath: metadata.name
      image: registry.redhat.io/oadp/oadp-velero-restic-restore-helper-rhel9@sha256:d2c7da625f2d1c6d54f6eb62d247acdc542e3a065f7e89c62e371b946a77c7e5
      imagePullPolicy: IfNotPresent
      name: restore-wait

Expected results:
Velero should skip the restoring of initContainer spec.

Environment:

• Velero version (use velero version):
  • v1.12
• Velero features (use velero client config get features):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
  • aws
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"