Currently midstream projects under the https://github.com/openshift-service-mesh/ organization run their jobs using OpenShift Prow, mainly because we need either run the jobs against a real OopenShift cluster (Istio, Sail), or because we need powerful machines (Proxy).

Prow configuration is complicated and frequently needs some changes, for instance, when Hypershift stops working.

On the other hand, if we already have the AWS credentials, we can create OCP clusters ourselves. In fact some of us already do that using the openshift-installer with our own credentials.

Benefits of moving to GitHub actions:

• Gives us total control of the testing environment, in contrast with relying on another team.
• Put the testing platform next to the repository and branch it's being used, rather than in a separate repo with different owners and workflow
• More agility and more automated tasks
• [more]?

Cons:

• any?
•  

If there is a reusable GitHub action that is capable of spawning a OCP cluster on AWS, we could just give it a try. If not, maybe we could try enhancing any existing similar one or in the worst case, create one.