Description of problem:

Customer wants to be able to deploy a Route with a custom hostname for Observability Grafana, instead of the default grafana-open-cluster-management-observability.apps.domain.com. 

Possible options are as follows:
1. To be able to specify via the MultiClusterObservability CRD a custom hostname for the observability-grafana Route
2. To be able to deploy an additional Route with a custom hostname for the observability-grafana Service
3. All the previous options 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info:

As a collaboration note, I tested in my lab and worked the following procedure to deploy an additional Route with a custom hostname:
1. Create a custom Route

$ oc get route grafana -n open-cluster-management-observability -o yaml > grafana-custom-route.yaml
$ sed -i "s/^  name: grafana$/  name: grafana-custom/g" grafana-custom-route.yaml
$ sed -i "s/host:.*$/host: grafana.apps.domain.com/g" grafana-custom-route.yaml
$ oc apply -f grafana-custom-route.yaml
$ oc -n open-cluster-management-observability patch route grafana-custom -p '{"metadata": {"ownerReferences":null}}'

2. Patch ServiceAccount `grafana`

$ oc annotate sa grafana serviceaccounts.openshift.io/oauth-redirectreference.grafana2='{"kind":"OAuthRedirectReference","apiVersion":"v1","reference":{"kind":"Route","name":"grafana-custom"}}'

3. Patch oauthclient `grafana-proxy-client`

$ oc patch oauthclient grafana-proxy-client -p $'redirectURIs:\n - https://grafana.apps.domain.com'

4. Restart observability-grafana pods

$ oc get pods -n open-cluster-management-observability | awk '/observability-grafana/ { print $1 }' | xargs oc delete pods

5. Access to the custom Route via the Web UI 

Testing environment:

• OCP v4.10.43
• RHACM v2.6.3