REQUEST: Migrate dims/hydrophone to kubernetes-sigs/hydrophone

[dims]

New repo, staging repo, or migrate existing

https://github.com/dims/hydrophone

Is it a staging repo?

no

Requested name for new repository

hydrophone

Which Organization should it reside

kubernetes

Who should have admin access?

dims rjsadow

Who should have write access?

dims rjsadow

Who should be listed as approvers in OWNERS?

dims rjsadow aniruddha2000

Who should be listed in SECURITY_CONTACTS?

dims rjsadow aniruddha2000

What should the repo description be?

Hydrophone is a lightweight Kubernetes conformance tests runner

What SIG and subproject does this fall under?

sig-testing sig-release

Please provide references to appropriate approval for this new repo

https://groups.google.com/g/kubernetes-sig-testing/c/OchiSDspgFU/m/r0SQvXX4AwAJ

Additional context for request

No response

[dims]

cc @jeremyrickard @justaugustus @saschagrunert @Verolop @cpanato @puerco @kubernetes/sig-release-leads

cc @jbpratt @michelle192837 @xmcqueen @BenTheElder @alvaroaleman @aojea @cjwagner @pohly @kubernetes/sig-testing-leads

[pohly]

👍 from me.

It will be very useful to run conformance testing more or less like real users will before cutting a release. I was discussing this with @hh a bit but we did not make much progress towards that with Sonobuoy.

[cpanato]

+1 this is nice

[aojea]

+1

[jbpratt]

+1 🎉 nice!

[xmudrii]

+1

[upodroid]

+1

[jeremyrickard]

+1 from me for SIG Release

[BenTheElder]

+1, as SIG Testing TL (also @pohly #4654 (comment) and @aojea #4654 (comment) above)

[neolit123]

@dims i'm trying to understand what the actual motivation is.

the project is certainly light weight in terms of LoC - https://ghloc.vercel.app/ reports it's 1/100 of the size of sonobuoy.
but sonobuoy also has plugin support and 50% of the LoC there are the "website".
in the README of hydrophone "lightweight" seems to be the main argument for it's existence, but perhaps another reason is "community owned"? i don't know if sonobuoy ever had plans to donate to the k8s orgs, either.

either way, +1 from me because of the community owned and lightweight factors, but -1 due to the OSS fragmentation.

[MadhavJivrajani]

/assign

Based on the +1s above from SIGs testing and release, I'll take this up and help create the repo.

[MadhavJivrajani]

@dims - question: what subproject of sig-testing/sig-release would this fall under?
I would think conformance, but that is a part of sig-arch.

[dims]

Let's do sig-testing please. it's mostly related to running tests. but with a audience of conformance testers

[MadhavJivrajani]

The repo has been migrated here: https://github.com/kubernetes-sigs/hydrophone 🎉

PRs to add GH teams and add hydrophone to sig-testing are open:

• config: add teams for hydrophone under k-sigs/sig-testing #4667
• sig-testing: add hydrophone repo community#7676

@dims @rjsadow, just FYI, the issue description mentions aniruddha2000 to be part of the OWNERS as well as SECURITY_CONTACTS. However, that does not reflect what those files actually hold currently, please either edit the issue or the respective files in the k-sigs/hydrophone repo.

[rjsadow]

@MadhavJivrajani addressing in kubernetes-sigs/hydrophone#79

[MadhavJivrajani]

Closing this out now, thanks all!

/close

[k8s-ci-robot]

@MadhavJivrajani: Closing this issue.

In response to this:

Closing this out now, thanks all!

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.