Catalog source affinity

[Jamstah]

Description of the change:

Add affinity customization to catalog sources

Closes #2960

Motivation for the change:

Enable multi-architecture catalog images to limit scheduling to their supported architectures.

Architectural changes:

n/a

Testing remarks:

Basically a copy paste of the same thing for tolerations.

Reviewer Checklist

• Implementation matches the proposed design, or proposal is updated to match implementation
• Sufficient unit test coverage
• Sufficient end-to-end test coverage
• Bug fixes are accompanied by regression test(s)
• e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
• tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
• Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
• Docs updated or added to /doc
• Commit messages sensible and descriptive
• Tests marked as [FLAKE] are truly flaky and have an issue
• Code is properly formatted

[openshift-ci]

Hi @Jamstah. Thanks for your PR.

I'm waiting for a operator-framework member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[Jamstah]

Opened as a draft, partly to let the tests run, and partly to ask a question.

The API change hasn't been put into a release yet - is that something I should wait for before finalizing the PR?

[perdasilva]

/ok-to-test

[perdasilva]

Opened as a draft, partly to let the tests run, and partly to ask a question.

The API change hasn't been put into a release yet - is that something I should wait for before finalizing the PR?

Hi @Jamstah - thanks heaps for this ^^
Yeah, I think we should cut a release of the api repo, then update the mod file to point to it before we can merge this PR.
I'll reach out to the team to see if we can get that happening.

[Jamstah]

Great. LMK when that's happened and I can rebase and revendor.

[Jamstah]

OK, should be all done.

[kevinrizza]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jamstah, kevinrizza

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 [kevinrizza]

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