• When a user creates a TempoStack from Tempo operator in a regular namespace, user can access the Tempo Jaeger Query console from: 

Go to Networking → Routes and Ctrl+F to search for tempo.
In the Location column, open the URL to access the Tempo console.
Select Log In With OpenShift to use your cluster administrator credentials for the web console.

• When a user creates a TempoStack in an OSSM SMMR member namespace, the Tempo Jaeger Query console is not accessible from the above Route.

There is a requirement from OSSM side to provide an option of configuring Tracing without OTEL. In that case, a Tempo Stack must be created in a SMMR member namespace. Otherwise, istiod service registry cannot find the Tempo distributor svc host.
We need a way of accessing Tempo jaegerQuery UI in the following how to produce steps:

How to produce:

• From an OCP cluster, install OSSM operator and Tempo operator
• Create namespaces, "istio-system", "tracing-system"
• Create a SMCP using the default CR yaml. For example,

kind: ServiceMeshControlPlane
apiVersion: maistra.io/v2
metadata:
  name: basic
  namespace: istio-system
spec:
  addons:
    grafana:
      enabled: false
    jaeger:
      install:
        storage:
          type: Memory
    kiali:
      enabled: false
    prometheus:
      enabled: false
  policy:
    type: Istiod
  telemetry:
    type: Istiod
  tracing:
    sampling: 10000
    type: None
  version: v2.4

• Create a SMMR as below:

  kind: ServiceMeshMemberRoll
  apiVersion: maistra.io/v1
  metadata:
    name: default
    namespace: istio-system
  spec:
    members:
      - tracing-system
  

• Create a Tempo Stack in namespace tracing-system
• Verify all tempo pods are running and ready
• Access the Tempo Jaeger Query console from: 
  Go to Networking → Routes and Ctrl+F to search for tempo.

Current behavior: the route is not working.

Expected behavior:
Tempo should provide a queryFrontend access configuration other than the ingress.type: route. And user should be able to access jaegerQuery UI when a Tempo Stack in created in a SMMR member namespace