please set a user agent

[BenTheElder]

It took me a while to track down

container-security-operator/secscan/wellknown.go

Line 15 in 10dfac7

wellKnownEndpoint = "/.well-known/app-capabilities"

and since there's no user agent set I can't be certain ... but we get a LOT of requests to https://registry.k8s.io for this non-standard endpoint (which isn't in the OCI registry spec nor https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml) and they all have generic Go HTTP client as the user agent.

Please consider setting a user agent so server operators know what the client is.

[BenTheElder]

... also, is there anything we can do to avoid users attempting to scan this API against registry.k8s.io? This seems to be something quay specific ...?

(not important, just seems odd to see a quay-specific API being accessed on other hosts ...?)

[HammerMeetNail]

Hey @BenTheElder , I created https://issues.redhat.com/browse/PROJQUAY-7472 for us to track. This seems like a straightforward ask, we'll review on Monday and work to roll it into a z-stream release in the coming weeks. We'll talk through hitting that path on other hosts too and get back to you.

[BenTheElder]

Thanks!