-
Notifications
You must be signed in to change notification settings - Fork 331
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
Add a new mechanism for requeuing a key. #2201
Conversation
This is modelled after some of the semantics available in controller-runtime's `Result` type, which allows reconcilers to indicate a desire to reprocess a key either immediately or after a delay. I worked around our lack of this when I reworked Tekton's timeout handling logic by exposing a "snooze" function to the Reconciler that wrapped `EnqueueAfter`, but this feels like a cleaner API for folks to use in general, and is consistent with our `NewPermanentError` and `NewSkipKey` functions in terms of influencing the queuing behaviors in our reconcilers via wrapped errors. You can see some discussion of this here: https://knative.slack.com/archives/CA4DNJ9A4/p1627524921161100
UT failed with:
|
I haven't touched that and can't rerun it because I'm not an editor. |
Yeah, I'm rerunning them :) Just adding a hold so the other folks from the thread have a chance to take a look. If they don't have concerns, I'll remove the hold tmw morning. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mattmoor, vaikas 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 |
Codecov Report
@@ Coverage Diff @@
## main #2201 +/- ##
==========================================
+ Coverage 65.98% 66.04% +0.05%
==========================================
Files 220 220
Lines 9207 9220 +13
==========================================
+ Hits 6075 6089 +14
+ Misses 2861 2860 -1
Partials 271 271
Continue to review full report at Codecov.
|
/unhold |
Looks like we want codegen to not emit an event for these too, so I'll have a small follow-up shortly. |
Changes
This is modeled after some of the semantics available in controller-runtime's
Result
type, which allows reconcilers to indicate a desire to reprocess a key either immediately or after a delay.I worked around our lack of this when I reworked Tekton's timeout handling logic by exposing a "snooze" function to the Reconciler that wrapped
EnqueueAfter
, but this feels like a cleaner API for folks to use in general, and is consistent with ourNewPermanentError
andNewSkipKey
functions in terms of influencing the queuing behaviors in our reconcilers via wrapped errors.You can see some discussion of this here: https://knative.slack.com/archives/CA4DNJ9A4/p1627524921161100
/kind enhancement
Release Note
Docs
Shouldn't have user-facing docs impact.