Epic Goal

• Support enabling workload partitioning from the installer without requiring manually created manifests.

Why is this important?

• The UX for creating manifests isn't great, and it exposes implementation details that we don't want the user to have to think about.

Scenarios

1. Enabling workload partitioning on single-node.
2. Enabling workload partitioning on multi-node.
3. Enabling workload partitioning with multiple node pools.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://github.com/openshift/installer/pull/4802
2. https://github.com/openshift/enhancements/blob/master/enhancements/management-workload-partitioning.md 
3. https://github.com/openshift/enhancements/pull/753

Open questions::

1. The install-config schema/API for specifying the partition(s) needs to be designed.
2. We don't have a full idea of how workload partitioning will look on multi-node or multiple node pools- This needs more design.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>