-
Notifications
You must be signed in to change notification settings - Fork 502
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
GEP 3388 Retry Budget API Design #3573
base: main
Are you sure you want to change the base?
GEP 3388 Retry Budget API Design #3573
Conversation
Hi @ericdbishop. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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-sigs/prow repository. |
75e5d0b
to
78667d6
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ericdbishop The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind gep
What this PR does / why we need it:
Following up on #3488, where GEP 3388 was moved to
provisional
and the general goals and some potential designs for retry budgets within Gateway API were agreed upon. This PR will present multiple API implementations based off of previous discussion.Which issue(s) this PR fixes:
Fixes #3388
Does this PR introduce a user-facing change?: