As described in DR, scs-0200-v1-using-sonobuoy-for-kaas-conformance-tests.md, it was decided to use sonobuoy as framework to deploy tests to Kubernetes clusters.

The current Sonobuoy setup within the repository was merely a PoC. We want to make it ready for production use.

The following must therefore be adjusted/implemented:

urgent

• Implementation of the Golang test framework in accordance with the PoC (see: kaas-sonobuoy-go-example-e2e-framework )
  • restructure directories
  • rework Makefile
  • minimal kind cluster setup for development
  • introduce linter https://golangci-lint.run/
• Upgrade golang version: Fix golang version in example Dockerfile #747

low priority

• ZuuL job to create the Sonobuoy image and upload it to the Github container registry
  • apply multi platform builds using the multi-arch setup
  • rework plugin config to dynamically chose image tag
  • check go sum file
• Zuul job to run the conformance test: [Feature Request] enable compliance tests to use plugins for cluster provisioning #710
• Write documentation on how you can contribute new tests. As part of docs/issues/201
• multi-arch support for arm64 and amd64 Add multi-arch support for amd64 and arm64 into Dockerfile #758