Dave Protasowski

Turning on request (& probe) logging it shows that the `activator` component is behind these probes. It triggers the queue proxy to perform the Pod's readiness check. The activator performs...

FYI In the past - the activator probe didn't trigger the queue proxy to perform a probe. Instead it would return the last known result of the queue-proxy probe.

> I think this is still kinda true. The way I'm interpreting [this probe code](https://github.com/knative/serving/blob/main/pkg/queue/readiness/probe.go#L106-L127) is that, it stores the last known probe, so that if a request to probe...

Hey @kahirokunn so our Revision's K8s service endpoints is manually managed by our ServerlessService controller here https://github.com/knative/serving/blob/main/pkg/reconciler/serverlessservice/serverlessservice.go But I believe even settings hints won't help as the activator performs it's...

I don't have a great answer to your problem. You could try and run distinct clusters in the same AZ (with Knative deployed to each one) and perform some global...

@skonto you confirm this is a dupe of https://github.com/knative/serving/issues/13677 and move your repro case there and close this issue?

/remove-lifecycle stale

Pairing with @kauana - we've discovered a few things First the migrator job is doing extra patches when it shouldn't need to filed an issue here- https://github.com/knative/pkg/issues/2845 Oddly the empty...

> I think first of all we should start with adopting non-root for any images in our [docs](https://knative.dev/development/) including hello world. I agree > Then, it would be better to...

> Sounds good. Can I create an issue to make all [serving code samples](https://knative.dev/docs/samples/serving/) run as non-root? Yup sounds good