Epic Goal

• Officially support 'us-east5' GCP region for OCP

Why is this important?

• This region is not part of the officially supported regions in GCP for OCP and users/customers are looking to deploy OCP in this region

Scenarios

1. As a user, I want the OpenShift Installer to list 'us-east5' 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>