ci: add konflux test cases

[yih-redhat]

To enable integration test in konflux, this pr added test cases that will be triggered by konflux mr https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/2167

This pr only includes simple check for those containers, after this pr and related konflux mr get merged, I can start to trigger the workflow and debug errors. After the whole konflux integration test workflow is verified, more test cases can be added later.

I have a concern:
konflux will build single fido container and trigger test, for example, it build manufacturing server container and then trigger test for manufacturing server. Konflux currently cannot build all fido containers at the same time and then trigger the test.
This brings two questions:

1. If I remember correctly some fido container depends on other container to start, so if that fido container can not startup, we can only run some very simple checks.
2. We need all fido containers up and running to run a full fido onboarding test, test each fido container separately does not make much sense.

[yih-redhat]

@mmartinv @runcom could you please help to review this pull request? (sorry I don't know which one of you I should ask)

[runcom]

1. If I remember correctly some fido container depends on other container to start, so if that fido container can not startup, we can only run some very simple checks.

not really, they can start independently but the value of testing them w/o the full flow is not high (to me, it's good but not high)

2. We need all fido containers up and running to run a full fido onboarding test, test each fido container separately does not make much sense.

yes

[henrywang]

Hi @yih-redhat, according to https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/2167#note_13160582, I think this PR needs to be landed first, then https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/2167.

[lukaszachy]

Hi @yih-redhat, according to https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/2167#note_13160582, I think this PR needs to be landed first, then https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/2167.

That would certainly be a best scenario, however if you expect this PR to be merged within few hours I can approve the configuration one (and merge it) ASAP.

The main risk is that automated MR (caused by Konflux references updates or package updates) are merge now automatically, which would stop if the tests suddenly do not pass

[miabbott]

Thanks for starting on this @yih-redhat!

I would love to see some additional documentation or inline comments explaining some of what is happening in these tests. For example, it is surprising to see the use of apk in the test (though I guess that is just the Testing Farm CLI container that is using Alpine Linux?).

I just want to avoid the situation where a new contributor to this repo finds these files and has no context about why they are here, what they do, etc.

[yih-redhat]

Hi @miabbott , I have add a README file in this konflux folder to explain why we created these files and what they do, and also explained the workflow that konflux use these files to run integration test. Please let me know if I miss anything here.