We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This line: https://github.com/vmware-tanzu/sonobuoy-plugins/blob/main/cis-benchmarks/kube-bench-plugin.yaml#L60C1-L60C1
which was changed in this commit on Oct 2 2023: fee2696
points to kube bench 0.6.17, but in the docker registry, 0.6.17 is the onlyarm image: https://hub.docker.com/layers/sonobuoy/kube-bench/v0.6.17/images/sha256-e031ba8457a8e2c5823533dd8aa7c57b67de0c9298cba949669bd4a4edd022c9?context=explore
arm
you can see the rest are amd https://hub.docker.com/r/sonobuoy/kube-bench/tags
amd
so this commit changed the architecture, which of course causes the pod to crash on amd kubernetes clusters
when I reverted the yaml (for the plugin) from 17 to 12, things worked as expected
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This line: https://github.com/vmware-tanzu/sonobuoy-plugins/blob/main/cis-benchmarks/kube-bench-plugin.yaml#L60C1-L60C1
which was changed in this commit on Oct 2 2023: fee2696
points to kube bench 0.6.17, but in the docker registry, 0.6.17 is the only
arm
image: https://hub.docker.com/layers/sonobuoy/kube-bench/v0.6.17/images/sha256-e031ba8457a8e2c5823533dd8aa7c57b67de0c9298cba949669bd4a4edd022c9?context=exploreyou can see the rest are
amd
https://hub.docker.com/r/sonobuoy/kube-bench/tags
so this commit changed the architecture, which of course causes the pod to crash on
amd
kubernetes clusterswhen I reverted the yaml (for the plugin) from 17 to 12, things worked as expected
The text was updated successfully, but these errors were encountered: