Epic Goal

Within HyperShift there are two modes for infrastructure management:

• Managed: HyperShift is responsible for the bootstrap and lifecycle management of all infra components (e.g., LBs, VPC, SG,...). 
• Un-managed: Guest cluster end users are respobsilbe for the bootstrap and lifecycle management of infrastructure required to provision a cluster. 

The goal of this Epic is to implement unmanaged mode for AWS. 

 A [CAEP|https://github.com/kubernetes-sigs/cluster-api/pull/4135] was proposed upstream to introduce "unmanaged" mode for infrastructure across different cloud providers in CAPI. 

Why is this important?

This addresses BYO infrastructure for cloud-based HyperShift deployments. 

Scenarios

• As a cluster provider, I want to use HyperShift in my service offering to orchestrate OpenShift bootstrapping while letting workload cluster operators own their infrastructure lifecycle.
• As a cluster operator, I want to use HyperShift to orchestrate OpenShift bootstrapping while restricting the privileges I need to grant for my cloud provider because of organizational cloud security constraints.
• As a cluster operator, I want to use HyperShift to orchestrate OpenShift bootstrapping while reusing infrastructure that has already been created in the organization either by me or another team.

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>