Epic Goal

• Users of OpenShift may have common, specific use cases they would like to implement in multi-arch clusters that they otherwise wouldn't usually need to think about. Examples of this would be using secondary scheduler plugins to control how workloads are distributed across architectures, or storage configuration across pools of different architectures. The goal of this epic is to review our available documentation for improvements we can make to present users with these most common uses cases.
• Specifically, the goal of the operator is to identify any best-practices to be used with these operators:
  • Secondary scheduler
  • Descheduler
  • Storage Operators (this covers different CSI plugins like IBM spectrum scale/fusion, OCS, etc)
  • Builds (this will probably be covered externally of this epic, since builds is it's own initiative)

Why is this important?

• …

Scenarios
1. …

Acceptance Criteria

• (Enter a list of Acceptance Criteria unique to the Epic)
• …

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'.