Move Openshift tests from Zuul to Testing Farm

[majamassarini]

After a deeper look, we can summarize this epic in the following steps:

• Automatically bootstrap Openshift Local in a local VM and run successfully one of our tests there (see Test deployment locally with tmt #562)
• Re-create the same environment used locally in a Testing Farm public bare metal instance [Move Openshift tests to Testing Farm] Bootstrap OpenShift Local on a Testing Farm bare metal instance #563
• Enable secrets in Testing Farm instance [Move Openshift tests to Testing Farm] Enable secrets #564
• Execute successfully the first test on Testing Farm [Move Openshift tests to Testing Farm] Run deployment test successfully #565
• Migrate all other openshift tests we have to Testing Farm and enable them in CI pipelines [Move Openshift tests to Testing Farm] Move all tests and enable CI #566
• optional Optimize test time execution using Snapshots (if execution time in CI is too long)

---

Description

We decided to setup an Openshift cluster in Testing Farm to move there the tests (at least those which needs openshift) of this repos:

• deployment
• packit-service
• sandcastle

The strimzi project has a k8s cluster setup for testing farm.

David told me:

we do install k8s cluster in scope of prepare steps in tmt plan. We used minikube and now we migrated to kind which also allows us to use multi node k8s cluster and support for ipv6.

plan:
https://github.com/strimzi/strimzi-kafka-operator/blob/main/systemtest/tmt/plans/main.fmf#L89

setup-kind:
https://github.com/strimzi/strimzi-kafka-operator/blob/main/.azure/scripts/setup-kind.sh

Probably we can start easy with minikube, following their example, and later if needed replacing it with an openshift instance...

This is a follow-up from packit/research#210

[majamassarini]

Probably the best thing is to start with the Openshift instance (Matej already gave a look at minikube and probably it is not worth spending time on it).