@nutritious-tomato-14686 ive been trying to write a doc for hydrophone highlighting how its used in different CICD system. https://github.com/kubernetes-sigs/hydrophone/issues/260 i believe k3s uses hydrophone for conformance test https://github.com/k3s-io/k3s/pull/11643. Would be grateful if you could mention the high level steps of how hydrophone is integrated in k3s cicd systems.

We use sonobuoy, same as upstream Kubernetes

oh the proposed changes in the PR said the following which made me think otherwise!

Proposed Changes
Convert the sonobuoy docker bash tests into the new go docker framework. Replaced sonobuoy with hydrophone.

There's a mix. We use that for some things, and full sonobuoy for others, and some are just plain testing. We also run the upstream sonobuoy conformance tests.

Thanks

We have replaced sonobuoy with hydrophone almost completely Brad in our CI system. Hydrophone is integrated directly into the go test framework https://github.com/k3s-io/k3s/blob/master/tests/docker/conformance/conformance_test.go This test runs conformance chunks (serial or parrallel) within our ginkgo/gomega framework. There are some workarounds for watching test progress. Results come to use looking like a standard ginkgo/gomega status result within CI logs.

upstream conformance is still all sonobuoy, and we run that as part of the docker tests on every PR

Thanks @nutritious-tomato-14686 for the help!