Epic Goal

• Feature Parity for Kubernetes SIG/RH Packaged - Scheduler Plugins
• Enable Power and s390x builds for Scheduler Plugins

Why is this important?

• Scheduling is a key component of workload management. Plugins enable customer specific/use case specific decisions to be made when scheduling the workload. e.g., to the closest NUMA node, the proper architecture, and many other decisions

Scenarios
1. As an OpenShift user, I want to schedule work based on plugins, and know it works on Power. https://github.com/kubernetes-sigs/scheduler-plugins#plugins

... I have obviated the plugin scenarios, as each needs to be evaluated for official support.

Acceptance Criteria

• There is an SIG container build that runs in MU supported architectures on OpenShift.
• The plugins load into the OpenShift Container Platform and can be used for decision making when scheduling workloads.

Dependencies (internal and external)
1. https://github.com/kubernetes-sigs/scheduler-plugins

2. This work should be done in parallel with Secondary Scheduler Operator

Previous Work (Optional)
1. Previous work was done in https://issues.redhat.com/browse/MULTIARCH-2886

The output is https://drive.google.com/drive/folders/1nv1KwQhcOfX7fy6No9zbIfLFL0iK94xC?usp=sharing

Open questions
1. Should we tack on another plugin to the RH Teleco Team's build?

2. Should we enable upstream with ppc64le / s390x?

3. Should we verify each architecture for each plugin?

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