Background

In order to ease troubleshooting, we need to provide access to the Perses UI from outside the cluster

Outcomes

• A route exists allowing access to the Perses UI 

Plan

On a technical level we can utilize the `https://github.com/openshift/oauth-proxy` repository to provide an authentication frontend for the Perses UI. Requests to the perses backend will then pass through the proxy and have the Authorization header added onto them for the backend to authenticate and authorize with.

1. Create a manual solution
   1. Use the sidecar method with the oauth-proxy
   2. Expose the oauth-proxy service as a route
2. Publish an internal use oauth-proxy image
3. Transform the manual solution into an automated solution in obo, adding a new image variable to be passed in for the oauth-proxy

Unknowns

• How do we handle including a repo we don't own into konflux?
• Is the oauth proxy able to be used across all versions of Openshift?
• Should we look to add the new application to konflux now or wait until we are closer to the 1.5 release?