Oadp velero pod affinity

[mpryc]

Why the changes were made

Follow up fix for the https://issues.redhat.com//browse/OADP-5832

This fixes Velero pod affinity, other PRs are for the node-agent and repository maintenance jobs.
That is why this also modifies design doc to include velero pod.

How to test the changes made

Testing is very similar to the testing for the #1683 (comment)
Except the config should include spec.configuration.velero.loadAffinity options. Please refer to the design doc as this setting can work together with the spec.configuration.velero.podConfig.nodeSelector field.

Number of tests were written to cover simple and more complex scenario, also make tests runs them.

apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
  name: <dpa_sample>
spec:
...
  configuration:
    velero:
      loadAffinity:
        nodeSelector:
          matchLabels:
            kubernetes.io/hostname: node3
          matchExpressions:
            - key: node-role.kubernetes.io/backup
              operator: In
              values:
                - true

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[mpryc]

/unhold

[mpryc]

/retest

[sseago]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpryc, sseago, weshayutin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mpryc,sseago]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mpryc]

/cherry-pick oadp-1.5

[openshift-cherrypick-robot]

@mpryc: new pull request created: #1716

In response to this:

/cherry-pick oadp-1.5

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-sigs/prow repository.