Add route label to LatestCreatedRevision#7110
Add route label to LatestCreatedRevision#7110knative-prow-robot merged 8 commits intoknative:masterfrom
LatestCreatedRevision#7110Conversation
knative-prow-robot
left a comment
There was a problem hiding this comment.
@tanzeeb: 0 warnings.
Details
In response to this:
Fixes #6733
Proposed Changes
- Add additional scenarios to the
MinScalee2e tests to checkminScaleduring the update of a configuration.- Add a route label to the
LatestCreatedRevision. This ensures continuity of areachablerevision when a configuration is updated.Release Note
The `LatestCreatedRevision` of a Configuration will now have a route label. Fixes issue where a Revision's pods are temporarily scaled below `minScale` after the Revision becomes ready.
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.
|
/assign @vagababov |
vagababov
left a comment
There was a problem hiding this comment.
Thanks @tanzeeb
/cc @mattmoor @markusthoemmes
0e75728 to
24ef148
Compare
* faster polling (250 ms) * more descriptive error for ensureDesiredScale * inlined latestCreatedRevisionName check
24ef148 to
35aa45e
Compare
|
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-knative-serving-autotls-tests: |
|
/assign @mattmoor |
| // If we are tracking the latest revision, we need to label the latest created revision | ||
| // as well so that there is a smooth transition when the new revision becomes ready. | ||
| if tt.LatestRevision != nil && *tt.LatestRevision { | ||
| revisions.Insert(config.Status.LatestCreatedRevisionName) |
There was a problem hiding this comment.
@vagababov @markusthoemmes it is tempting to also label the LCR with the LRR in this case so that the KPA gets a hint about how big to make the LCR before it is receiving traffic 🤔
mattmoor
left a comment
There was a problem hiding this comment.
Thanks, this looks about right. Couple nits, but otherwise 👍
|
The following is the coverage report on the affected files.
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mattmoor, tanzeeb 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 |
* Test minScale during update to configuration * Add route label to LatestCreatedRevision * Use impl.Enqueue instead of tracker.OnChanged in labeler reconciler * Update minscale readiness e2e test * faster polling (250 ms) * more descriptive error for ensureDesiredScale * inlined latestCreatedRevisionName check * Enqueue route instead of config in labeler reconciler * Only label configurations of RunLatest traffic targets * Label configuration if it or it's revision is in a route * Only pull config for runLatest in labeler
* Add route label to `LatestCreatedRevision` (#7110) * Test minScale during update to configuration * Add route label to LatestCreatedRevision * Use impl.Enqueue instead of tracker.OnChanged in labeler reconciler * Update minscale readiness e2e test * faster polling (250 ms) * more descriptive error for ensureDesiredScale * inlined latestCreatedRevisionName check * Enqueue route instead of config in labeler reconciler * Only label configurations of RunLatest traffic targets * Label configuration if it or it's revision is in a route * Only pull config for runLatest in labeler * Some cleanups in the e2e test (#7193) * Some cleanups in the e2e test * Some cleanups in the e2e test * fix nit * Simplify minscale test. (#7235) The only error returned from the function is when we fail to actually verify the scale. So return boolean instead. * Fix minscale on deploy (#7214) * Test minscale stability when configuration is created * Check both .spec.traffic and .status.traffic for resources to label * Inline condition * Inline owner reference check Co-authored-by: Tanzeeb Khalili <tkhalili@pivotal.io> Co-authored-by: Victor Agababov <vagababov@gmail.com>
Fixes #6733
Proposed Changes
MinScalee2e tests to checkminScaleduring the update of a configuration.LatestCreatedRevision. This ensures continuity of areachablerevision when a configuration is updated.Release Note