Add OpenShift docs note on exposing UI in-cluster with Routes (#2474)

This is an openshift-specific setting, and it can be different depending
on the cluster, so there isn't much we can guide users on. But making
them aware of the right service to expose is helpful.

In my AWS OpenShift cluster, for example, I needed to set
`tls.termination: edge` manually on the Route (it doesn't seem to be a
cli setting in `oc expose`).

docs/setup/installation-options.mdx

@@ -75,3 +75,20 @@ from `registry.connect.redhat.com/odigos`. These images are based on
 the `-ubi9` suffix. These images are also hosted on the Odigos
 DockerHub registry, which you can deploy by setting `--openshift` with
 `--image-prefix docker.io/keyval`.
+
+### Exposing the Odigos UI via OpenShift Routes
+
+To access the Odigos UI in OpenShift, use either the standard `odigos
+ui` command or create a `Route` that exposes the `ui` service on your
+cluster's external address. For example:
+
+```
+oc expose service ui -n odigos-system
+```
+
+Then get the external address for the Route with `oc get routes ui -n
+odigos-system`.
+
+Check the OpenShift documentation or run `oc expose -h` for more
+information on configuring OpenShift routes according to your
+cluster's requirements.