What steps did you take and what happened:
I downloaded sonobuoy yesterday via homebrew as described in the README. As seen on the Homebrew formulae page, v0.57.4 is shown as the stable release: https://formulae.brew.sh/formula/sonobuoy.
I then executed a custom plugin we have built internally to run some tests against our cluster. Upon trying to start the tests, the sonobuoy pod entered ImagePullBackOff, failing to retrieve the 0.57.4 image from Dockerhub.
I then confirmed both Dockerhub and this Github repo lack releases for 0.57.4 still, almost 2 weeks after a commit hit master with that version.
What did you expect to happen:
I expected sonobuoy run to work without adding a specific --sonobuoy-image argument, and for the stable version on Homebrew to be fully released/supported.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
I did confirm the image version tag is the only issue - running with --sonobuoy-image docker.io/sonobuoy/sonobuoy:v0.57.3 is a valid workaround for now.
Environment:
- Sonobuoy version: 0.57.4
- Kubernetes version: (use
kubectl version): Client v1.32, Server v1.32.9-eks-3025e55
- Kubernetes installer & version: EKS Version 1.32
- Cloud provider or hardware configuration: AWS EKS
- OS (e.g. from
/etc/os-release): Ubuntu 22.04.4 LTS
- Sonobuoy tarball (which contains * below): N/A
What steps did you take and what happened:
I downloaded sonobuoy yesterday via
homebrewas described in the README. As seen on the Homebrew formulae page,v0.57.4is shown as the stable release: https://formulae.brew.sh/formula/sonobuoy.I then executed a custom plugin we have built internally to run some tests against our cluster. Upon trying to start the tests, the
sonobuoypod enteredImagePullBackOff, failing to retrieve the0.57.4image from Dockerhub.I then confirmed both Dockerhub and this Github repo lack releases for
0.57.4still, almost 2 weeks after a commit hitmasterwith that version.What did you expect to happen:
I expected
sonobuoy runto work without adding a specific--sonobuoy-imageargument, and for the stable version on Homebrew to be fully released/supported.Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
I did confirm the image version tag is the only issue - running with
--sonobuoy-image docker.io/sonobuoy/sonobuoy:v0.57.3is a valid workaround for now.Environment:
kubectl version): Client v1.32, Server v1.32.9-eks-3025e55/etc/os-release): Ubuntu 22.04.4 LTS