My sense is that using the Kubernetes API might be the best approach for initiation of the tests. Adding keel.sh is complicating the solution so I am looking for ways to avoid it. I am looking to use agola to reduce the variety of technologies a consumer of open source needs in order to successfully use CI/CD.
I would then have a step that waits for the test driver pod inside the test namespace to exit and then scrape the logs from the test driver pod and incorporate them as output inside the agola pod output. Finally deleting the test namespace as an additional final step.
As time permits I’ll try to prototype this approach.