John Howard

Not really. I did mean build_fuzzer not build_image, I must have gotten them mixed up. Without a mounted cache no matter what we do to the building logic it will...

That allows mapping the source to a specific location; the request would be to allow adding arbitrary mounts in https://github.com/google/oss-fuzz/blob/2fa71e3c7f87497dc31a9b236175c2173756fc99/infra/helper.py#L700 In this specific case (or probably all Go fuzzers, really)...

This is expected for now, there are quite a few places we assume IPv4

Regardless of if it's in the doc dramatically changing the functionality of an existing API is incompatible. Let's take a step back here. I haven't seen any discussion of the...

I still don't understand the use case. The issue you linked does not explain *why* they want this.

Doesn't Sidecar scoping handle this? In multitenant situations I would imagine its typical to not actually have *permission* to read from all namespaces?

I think this is a pretty important topic and should probably have a proper design. At the very least, we cannot change the behavior of the existing field or there...

> I haven't tested this, but the doc for sidecar workload selector (this is what you mean, right?) does not mention scoping for all CRs but only a handful? Does...

@kfaseela Gateways have namespace scoping options already: PILOT_SCOPE_GATEWAY_TO_NAMESPACE or use new Kubernetes Gateway API which has this as default

There are really 3 parts - discovery, CRDs, and configmap writing So do we want 3 selectors, 1 selector that does all of them (with temp flag for backwards compat),...