feat(delivery): add maximum backoff duration - #9279
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kahirokunn The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9279 +/- ##
==========================================
+ Coverage 51.06% 51.15% +0.08%
==========================================
Files 411 411
Lines 22120 22172 +52
==========================================
+ Hits 11295 11341 +46
- Misses 9951 9954 +3
- Partials 874 877 +3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
2ffc0ab to
7469149
Compare
828cffc to
2f36d16
Compare
|
/ok-to-test |
shouldn't be needed anymore for you as an org member :) |
|
@dsimansk Thank you! |
Signed-off-by: kahirokunn <okinakahiro@gmail.com>
2f36d16 to
93bc77a
Compare
Agreed, I've added one suggestion. Otherwise looks good, given it's feature flag guarded and well test covered. |
|
@dsimansk Thanks for the suggestion, I've addressed it! Could you take another look when you get a chance? 🙏 |
|
/test upgrade-tests |
This PR implements the Alpha stage of #9278.
TL;DR: New experimental feature allowing users to opt in to capping normal delivery retry intervals calculated from
backoffDelayandbackoffPolicy.Proposed Changes
delivery-backoff-maxfeature flag, disabled by default.DeliverySpecwith the optionalbackoffMaxfield.backoffMaxis a positive ISO 8601 duration and reject the field while the feature is disabled.backoffMaxthrough Subscription reconciliation and Channel delivery defaults.backoffMaxinRetryConfigFromDeliverySpec()and apply it to linear and exponential backoff calculations.time.Duration, including when no explicit maximum is configured.Retry-Afterindependently controlled byretryAfterMax.Pre-review Checklist
Release Note
Docs
📖 knative/docs#6686