{}USER STORY:{}

As an OpenShift developer, I would like to have quick access to deploy AWS variants not exercised in CI or requires customization not tracked by CI jobs, so i can quickly reproduce user-facing scenarios to reproduce issues in my environment and decrease the total time to answer issues.

{}DESCRIPTION:{}

This is an idea discussed with some SPLAT and Installer team members to provide somewhere to help developers to quickly access/reproduce installations (specially those more complex like UPI) to reproduce customer issues.

The quickest way for supported scenarios is using AWS CloudFormation template, although the current templates are tied to BYO VPC, requiring customization, and consume time for developers to do it. The idea of this card is to introduce a path/way to deploy custom Templates used by developers only to deploy locally.

The real example is BYO VPC scenario with multi CIDR blocks in VPC where machine CIDR is using a non-defaultt CIDR block: OCPBUGS-35054 

Another example is the CloudFormation templates (derivated from original from installer repo upi/aws/cloudformation) to deploy Platform External cluster on AWS on OCP CI. Those are saved on https://github.com/openshift-splat-team/installer-labs 

This is a "the tip of iceberg", I strong believe we need to introduce a path to use CloudFormation Nested Templates, then create stacks templates to consume existing nested templates, it will reuse and decrease a lot of new code added when writing variants. I wrote several examples for my labs here: https://github.com/mtulio/mtulio.labs/tree/devel/labs/ocp-install-iac/aws-cloudformation-templates

• where [0+]_* files are Templates for resources,
• and the stack_* files are Stacked Templates implementing the variants.

{}Required:{}

• Provide a "internal" repository where developers can quick access and deploy (providing quick guide) the variant
•  

{}Nice to have:{}

- 

{}ACCEPTANCE CRITERIA:{}

• A place accessed by any OpenShift developer
• We should state those documents are not tested and not "supported" to Customers 
• For each stack/variant, a devel document must be created to be used as a helper to quick start

Non-Goals:

• Test CloudFormation deployments by OpenShift CI/Prow

{}ENGINEERING DETAILS:{}

• https://github.com/openshift/installer/pull/8946
• https://issues.redhat.com/browse/OCPBUGS-35054
• OCPBUGS-35054: capi/aws/byo-vpc/multi-cidr: fix group rules #8591
• https://redhat-internal.slack.com/archives/C01V1DP387R/p1725397384465729?thread_ts=1725309991.578379&cid=C01V1DP387R
• https://github.com/openshift-splat-team/installer-labs