-
Notifications
You must be signed in to change notification settings - Fork 593
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
Change default Broker delivery spec #6011
Change default Broker delivery spec #6011
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pierDipi 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 |
0e7142b
to
b58af9b
Compare
Codecov Report
@@ Coverage Diff @@
## main #6011 +/- ##
=======================================
Coverage 82.32% 82.32%
=======================================
Files 225 225
Lines 7636 7636
=======================================
Hits 6286 6286
Misses 910 910
Partials 440 440 Continue to review full report at Codecov.
|
Signed-off-by: Pierangelo Di Pilato <pdipilat@redhat.com>
8d15bb9
to
d5d5997
Compare
This commit adds a delivery spec to `t2` to avoid assuming that the Broker delivery spec is empty by default. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
d5d5997
to
ee5eae0
Compare
LGTM, just need to socialize this more within the WG and our users before we merge it. @pierDipi was this already discussed during any WG meeting? |
Yes, this was discussed with you and @xtreme-sameer-vohra, we concluded that in addition to a better delivery guarantee by default, this also increases consistency across multiple broker implementations. |
related to #4440. /lgtm |
my volatile memory 🤦🏽♂️ /unhold |
When we changed the default retry parameters in knative#6011, the check to see if the webhook has observed the update isn't reliable anymore, this PR checks for the expected delivery parameter to ensure that the update was actually seen by the webhook. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
When we changed the default retry parameters in knative#6011, the check to see if the webhook has observed the update isn't reliable anymore, this PR checks for the expected delivery parameter to ensure that the update was actually seen by the webhook. Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>
Our Broker delivery spec is unset by default, which means that it has literally a
fire-and-forget delivery guarantee because with don't retry.
To make our defaults stronger, we should set a reasonable delivery spec
by default when no delivery spec is specified.
Default Delivery Spec
The following delivery spec isn't perfect for every use case by at least
prevents events loss for normal networking errors (eg connection resets, etc)
or during upgrades.
The retry period with the above configuration is ~200 seconds long
Fixes #5936
Proposed Changes
Pre-review Checklist
Release Note
Docs