Epic Goal

• This epic aims to consolidate the different tickets and efforts laid out by different teams in regards to what can be improved across the Operator Framework to improve the overall for developing on multi-arch and leveraging multi-arch compute nodes.

Why is this important?

• A comprehensive review of the multi-arch related aspects of operator support is a key part of ensuring that operator and layered products teams have unified expectations and standards for multi-arch support across the product. This in turn helps the user experience, because you can expect key tools to work the same on any platform where it's available.
• This epic captures the actions described by the CFE team in their initial efforts, but also collects some other tasks and improvements related the multi-arch validator that needed to belong to stories.

Scenarios
1. …

Acceptance Criteria

• Each of the stories in the linked PORTENABLE epics are reviewed for completeness and migrated to this epic, if necessary.
• Stories / epics are created to track and address additional steps to address weaknesses in Operator-Framework. As an example, https://issues.redhat.com/browse/PORTENABLE-378 seems like it should probably be a spike either tracked as part of this epic, or linked from this epic since it tries to identify changes to Operator Framework itself that haven't already been listed in that epic.
• Operator-SDK docs are updated to reflect the improvements in the validator already present upstream. (https://issues.redhat.com/browse/MULTIARCH-4682)
• Node affinity warnings are applied using set-intersection for images in a PodSpec/PodSpecTemplate (https://issues.redhat.com/browse/MULTIARCH-5035)

Dependencies (internal and external)
1. …

Previous Work (Optional):
1. …

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.