Activator: for reserved revision, wait for the revision to be ready and then send the request.

[akyyy]

Expected Behavior

When the traffic is routed to the activator, it should find the correct revision. Maybe add some header in the request.

Actual Behavior

The revision is found in activator using hard coded value:
revision, err := revisionClient.Get("configuration-example-00001", metav1.GetOptions{})

[akyyy]

josephburnett:
The Revision may be Active, but the Service may not have any endpoints in it. There is a delay between when the Revision.Spec is changed to Active and when the controller creates the resources and they all come online.

So I would expect that requests which arrive immediately after the first one will take this code branch, but get a 5xx error instead of reaching a Pod through the Service.

I suggest you don't worry about that right now. Just get this working. But create a separate issue to close the gap. You can either 1) retry on 5xx requests to the Service or 2) proxy all requests directly to Pods you find through labels (my preference for simplicity).

mattmoor:
I'd recommend Watching Revisions and the Revision's Status should have a Condition reflecting the readiness of the K8s Service.

[akyyy]

This is addressed in #341