Implement verification for route readiness for the runLatest.#2898
Implement verification for route readiness for the runLatest.#2898knative-prow-robot merged 12 commits intoknative:masterfrom
Conversation
TL;DR: knative#2430 - This is the first change to ensure that we mark service as ready only when all the subresources have successfully reconciled. - In this change runLatest is covered. The service will become ready only when config.LatestReadyRevision is the one served by the route. When they mismatch the service will transition into the `Unknown` state until route finishes reconciliation. - Unit tests are updated and extended for this case - Integration tests are hardened to make sure the service transitions into ready state before verifying request/responses.
|
/cc dgerd |
knative-prow-robot
left a comment
There was a problem hiding this comment.
@vagababov: 0 warnings.
Details
In response to this:
TL;DR: #2430
Proposed Changes
- This is the first change to ensure that we mark service as ready only
when all the subresources have successfully reconciled.- In this change runLatest is covered. The service will become ready
only when config.LatestReadyRevision is the one served by the route.
When they mismatch the service will transition into theUnknown
state until route finishes reconciliation.- Unit tests are updated and extended for this case
- Integration tests are hardened to make sure the service transitions
into ready state before verifying request/responses./lint
/cc dgerd
/cc mattmoor
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.
|
/test pull-knative-serving-go-coverage |
|
/cc @jonjohnsonjr |
|
/retest |
1 similar comment
|
/retest |
markusthoemmes
left a comment
There was a problem hiding this comment.
/lgtm
Left a few comments throughout, only nits though.
vagababov
left a comment
There was a problem hiding this comment.
Thanks for the comments.
|
/test pull-knative-serving-integration-tests |
- improve the functional helper name - removed the confusing comment - added a test that validates the proper behaviour when gen 2 config fails, but gen 1 is happy throughout.
|
/test pull-knative-serving-integration-tests |
|
/lgtm New test and changes lgtm |
|
/assign vaikas-google |
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vagababov, vaikas-google The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
Interface changed... have to merge and retest. |
- reason is a single word - move the validation from callback to the postprocessing.
|
PTAL. |
Co-Authored-By: vagababov <vagababov@users.noreply.github.com>
|
The following is the coverage report on pkg/.
|
|
/lgtm |
TL;DR: #2430
Proposed Changes
when all the subresources have successfully reconciled.
only when config.LatestReadyRevision is the one served by the route.
When they mismatch the service will transition into the
Unknownstate until route finishes reconciliation.
into ready state before verifying request/responses.
/lint
/cc dgerd
/cc mattmoor