Epic Goal

• Add support for Azure Stack Hub

Why is this important?

• Enabling customers - heavy focus for Public sector accounts - to deploy OpenShift 4 to an on-premise Microsoft Azure Stack Hub environment.
• Azure Stack Hub support is mandatory for many of North American Public Sector customers and will be a portion of the $10 Billion dollar Joint Enterprise Defense Infrastructure (JEDI) contact awarded to Microsoft.
• Canadian Government and many commercial customers are also interested in support: RFE-21

Scenarios

1. As an administrator, I would like to deploy OpenShift 4 clusters to an on-premise Azure Stack Hub environment leveraging cloud based networking, storage, and compute resources

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

Open questions::

1. …

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>