[processor/resourcedetection] Evaluate using Openshift in CI to E2E tests for openshift detector

[paulojmdias]

Have we considered testing against actual OpenShift cluster instead of mocking the response?

Given that for k8s we bring up actual kind clusters, I'd find this useful to have a similar approach here.

Originally posted by @ChrsMark in #45627 (comment)

[paulojmdias]

#45627 (comment)

This could also be evaluated to support E2E tests for other components if it makes sense.

[github-actions]

Pinging code owners:

• processor/resourcedetection: @Aneurysm9 @dashpole

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

Pinging code owners for processor/resourcedetection: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triage' to set the priority and remove the needs-triage label.

[iblancasa]

Maybe using https://github.com/marketplace/actions/microshift-openshift-cluster ... I tried in the past for the operator... but was not so successful.

[paulojmdias]

Maybe using https://github.com/marketplace/actions/microshift-openshift-cluster ... I tried in the past for the operator... but was not so successful.

That does not have updates for some years. I shared the one below on the PR since it seems being maintained https://github.com/crc-org/crc-github-action

[iblancasa]

It's fine. The problem we found was deploying the cluster was too slow and sometimes it failed without any obvious reason.