Epic Goal

• Officially support ap-southeast-4 /Melbourne AWS region for OCP before the end of Q1 2023.
• make available in a patch stream of 4.11, eg: 4.11.z so that Service Delivery can make the region available for OSD/ROSA customers.

Why is this important?

• This region is not part of the officially supported regions in AWS for OCP and users/customers are looking to deploy OCP in this region
• This is driven by request from our AWS partners for ROSA/OSD as well. The timeline (before end of September 2022) is driven by AWS and our SD org.

Scenarios

1. As a user, I want the OpenShift Installer to list 'ap-southeast-4' region so that I can deploy OCP on that region using IPI or UPI workflows

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• The OpenShift Installer is able to list the region for the user to select
• The region is included as a supported region in the documentation

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>