-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix LatestReadyRevision semantics - it only advances forward #13239
Fix LatestReadyRevision semantics - it only advances forward #13239
Conversation
The search for latest ready revision (LLR) looked at each revision's configurationGeneration label to search for a new candidate. Only Revisions with a configurationGeneration in a certain range were considered. Prior this inclusive range was [LLR.generation, config.generation]. The lower bound was incorrect and it should actually be LLR.configGeneration. Otherwise LLR generation is fairly low the the set of revision to consider would be quite large for really old Configurations.
Codecov ReportBase: 86.56% // Head: 86.48% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #13239 +/- ##
==========================================
- Coverage 86.56% 86.48% -0.09%
==========================================
Files 196 196
Lines 14505 14544 +39
==========================================
+ Hits 12556 12578 +22
- Misses 1650 1666 +16
- Partials 299 300 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Looks like BYO revision name has a broken edge case |
/hold for after 1.7 |
This is required to support git revert in combination with a Knative Service that has latestRevision: true in their Route traffic block
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Prior the conditional was not correct and the generation was not part of the selector. Also made sure the unit test failed prior to applying the fix.
/assign @psschwei @nader-ziada |
/hold cancel |
/lgtm |
Fixes #12538 #12078
Proposed Changes
From commit message
Release Note