John Schnake

Hm. So in this case you're just specifying the secret as an env var which has no expectation of privacy. In a generic sense, how would we know this env...

We currently build for Windows and Linux, including linux/arm64; I'm assuming the requesting user needed armv6 or v7? (Note that we build the binary for many more os/arch, that is...

You can look at the os/arch supported here https://hub.docker.com/layers/sonobuoy/sonobuoy/main/images/sha256-e49fd131e727455e548efbcb0e4e57140a6751f1e46017d82fa0d3dce6bd2a61?context=explore

https://kubernetes.io/releases/download/ shows the k8s build versions which includes an `arm` and `arm64`. GOOS supports an `arm` option which is a 32bit and that aligns with what the original post was...

@NikhilSharmaWe if you wanted a hand at updating docs (you offered to write a whole new page on another ticket) then this may be a bit easier since it is...

Trying out the feature is a bit frustrating since it requires pushing/pulling images to different repos and running the e2e tests. However, you could try and just set the env...

See https://github.com/vmware-tanzu/sonobuoy/pull/1237

https://github.com/onsi/ginkgo/issues/897

Based on the discussion in that linked ticket, the upstream k8s code needs some cleanup. There is already a way to customize timeouts but it hasn't been fully implemented throughout...

Is there a code example I could look at for how this is done manually? I can dig into API snoop but I'm not familiar with how it is currently...