Configure AWS EBS GP2 in default SC if running on Outpost

Epic Goal*

The OCP AWS EBS operator currently configures gp3 in the default storage class however when deploying outpost, gp3 is not available. This epic tracks the work required to change the default SC to use gp2 instead of gp3.

 
Why is this important? (mandatory)

Without this feature, customers who are deploying OCP on top of AWS Outpost will get an unusable default SC which degrades the user experience and goes against our approach to provide a working default storage class after deployment.

 
Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. When deploying OCP on top of AWS output the default storage class should be set to gp2
2. no action required from a user point of view.
3. GP3 should remain the same when not deploying on top of Output

 
Dependencies (internal and external) (mandatory)

1. We need to have an OCP API that the EBS operator can query to find out if OCP is running on top of Outpost.
2. We need to have CI jobs with OCP e2e tests configured and running on AWS outposts. We will add a CSI job for the CSI driver on outpotst, copying an existing one. 

Contributing Teams(and contacts) (mandatory) 

TBD - We need an OCP api that can detect that OCP is deployed on top of AWS Outpost and expose it to the EBS operator.

TBD - Who will configure CI for outposts?

Acceptance Criteria (optional)

Default SC is configured with gp2 without any user intervention + usual regression tests.

Drawbacks or Risk (optional)

Increase EBS operator complexity with custom cases, that is why we need to limit the changes and have an OCP API that exposes that OCP is running on top of Outpost

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be “Release Pending”