This epic tracks the design/implementation of getting UI tests working in the continuous delivery flow

Currently app-sre has a continuous delivery mechanism that allows teams to:

• merge changes to master/main
• auto-promote to stage
• auto-run a test in the stage env
• if the test passes, auto-promote to prod

The process for setting this up is documented here: https://consoledot.pages.redhat.com/docs/dev/getting-started/appsre/cd.html

A big gap in this approach currently is that the UI cannot be tested, only backend components can be tested via this approach. The IQE jobs get deployed into the stage OSD cluster, which is outside of the VPN. They are unable to reach the stage UI.

Possible options:
1. deploy the test jobs into another cluster inside the VPN (possibly requires some clowder reworking – the jobs currently are deployed as CJI's ... so they require a ClowdApp to be present in the namespace)
2. re-work app-sre's CD tooling to allow firing jenkins jobs (not only OpenShift jobs)
3. set up peering between the stage OSD cluster and RH corp so we can reach internal resources