Revisions should wait for minScale replicas to report ready

[mattmoor]

We discussed this in slack the other day, and I'm not sure an issue was opened to track it.

Basically the question was: if a Revision has minScale: 50 then should we still report Ready when only a single endpoint has come up?

I think the answer was fairly unanimous that it should not be considered Ready.

[mattmoor]

/milestone Serving "v1"

[knative-prow-robot]

@mattmoor: The provided milestone is not valid for this repository. Milestones in this repository: [Ice Box, Needs Triage, Serving "v1" (ready for production), Serving 0.4]

Use /milestone clear to clear the milestone.

Details

In response to this:

/milestone Serving "v1"

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[markusthoemmes]

/assign

need something to ramp up on a bit

[markusthoemmes]

Not getting to this in a short'ish timeframe. Unassigning for now, might come back later if nobody took it in the meantime

/unassign

[joshrider]

/assign

[knative-prow-robot]

@pivotal-joshua-rider: GitHub didn't allow me to assign the following users: pivotal-joshua-rider.

Note that only knative members and repo collaborators can be assigned.
For more information please see the contributor guide

Details

In response to this:

/assign

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.