Epic Goal

• Streamline onboarding of new AWS regions in OCP managed services like ROSA or OSD by removing the need for code changes in the cluster image registry operator

Why is this important?

• Every time AWS is launching a new region the deployment of OpenShift will fail with the Cluster Image Registry Operator failing to reconcile until the newly added region is hard coded into the operator's controller
• This blocks installer and QE teams from development, testing and rollout of new region support for OCP managed services on AWS 
• Disabling the integrated registry is currently not supported by many of our managed services

Acceptance Criteria

• A new AWS region should not require any code changes to CIRO for the operator to reconcile the request for required cloud infrastructure to run the image registry
• Backports to all currently supported OCP versions

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>