Nice project ! I have a question about spawning a Kubernetes test within a pipeline. Current I have cobbled together a pipeline that uses Makisu to build my images and then pushes these to the same Kubernetes cluster (microk8s) the build was performed in. Then I used keel to trigger a step where a pod spun up two containers with rabbitmq, and minio along with the container of the image under test. Once the test was finished the original build container was setting the replica count for the supporting pods to a count of 0 in order to bring down the test environment.
From reading the docs it appears I am set to go with Kaniko, and the builder container itself. What approach would you favor for going about setting up a namespace with pods etc as a downstream test of the produced image inside exactly the same cluster via the Kubernetes API ?
My fairly disorganized pipeline docs, studio-go-runner/ci.md at master · leaf-ai/studio-go-runner · GitHub.