Feature Overview (aka. Goal Summary)  

Ability for customers to use custom domain for the ROSA (HCP) cluster's component domains.

PRD document

Requirements (aka. Acceptance Criteria):

1. Ability to configure ROSA HCP Cluster console URLs for:
   1. Console
   2. OAuth
   3. Downloads
2. Allow configuring those URLs
3. Support these configurations in EDIT CLUSTER (instead of EDIT INGRESS)
   • Because these are part of cluster config in OCP/HCP
4. Ability to change individual URLs of
   1. Console
   2. OAuth
   3. Downloads 
5. Ability to change {namespace-route} without providing new TLS certificates
6. Ability to change FQDNs providing TLS certificates

Supported Clients	Option
Supported in ROSA cli	Yes ( ) No ( ) N/A
Supported in OCM cli	Yes ( ) No ( ) N/A
Supported in OCM UI	Yes ( ) No ( ) N/A
Supported in TF	Yes ( ) No ( ) N/A
Supported in Capi	Yes ( ) No ( ) N/A
Supported Offerings	Option
Fedramp supported?	Yes ( ) No ( ) N/A
OCP Support	Option
Is it already supported in OCP?	Yes ( ) No ( ) N/A
If Yes, what OCP version ?	n/a

Use Cases (Optional):

1. Customers change the {namespace-route} section without changing the base domain. This doesn't require a new TLS certificate since the same TLS certificate configured for base domain will be used.
2. Customers change FQDN, providing TLS Certificates corresponding to the FQDN. 
3. Customers use public certificates for public clusters or private certificates for private clusters 

Out of Scope

1. Editing default Ingress controller to configure Ingress Operator as laid out here: https://docs.openshift.com/container-platform/4.16/networking/ingress-operator.html#configuring-ingress-controller
2. Replacing default ingress certificate 
3. Adding features to ROSA EDIT INGRESS (Read more in XCMSTRAT-484)

Background

1. OpenShift instructions for customizing Console Route URL :https://docs.openshift.com/container-platform/4.16/web_console/customizing-the-web-console.html#customizing-the-console-route_customizing-web-console