Add a brew repo

[cprivitere]

Hey all, would like to start using this instead of sonobuoy, however you don't have a brew package yet. Would love to see that get added.

[dims]

@cprivitere no we don't yet. would you have cycles to help with that? (would be awesome!!)

[reetasingh]

@dims @cprivitere @rjsadow I am interested in working on this . I can assign this issue to myself if @cprivitere is fine with that

[cprivitere]

I sure don't mind. I don't really have the cycles at the moment.

[reetasingh]

PR opened Homebrew/homebrew-core#162309

[reetasingh]

@cprivitere @dims @rjsadow looks like we need more adoption for hydrophone to make it available on homebrew , see comment Homebrew/homebrew-core#162309 (comment)

[dims]

@reetasingh no worries. if enough folks chime in here or there (or we get some data on downloads) then we can ask them to revisit. thanks for trying!

[dims]

(ya, no need for that personal tap thing now)

[cprivitere]

When they say personal tap they just mean "not managed by the brew maintainers". This is what I expected us to create, a brewfile inside this repo that people could tap with brew tap kubernetes-sigs/hydrophone (or hydrophone-brew or kubernetes-tap or who knows what else, if separation is desired) and use to get updates. goreleaser can create them for you.

[dims]

@cprivitere that does not sound too bad! :)

[reetasingh]

@cprivitere I have created a draft PR #178 PTAL

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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-sigs/prow repository.