-
Notifications
You must be signed in to change notification settings - Fork 492
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
Retry Budgets in HTTPRouteRetry #3388
Comments
/assign @ericdbishop |
@mikemorris: GitHub didn't allow me to assign the following users: ericdbishop. Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
/assign |
Commenting so i can be assigned this. |
/assign @ericdbishop This issue has been included in the planned scope for the Gateway API v1.3 release - I'm planning to support @ericdbishop through the GEP process to help move this forward (and would welcome additional help from @rajatsharma94 @kflynn or others interested in this functionality too)! |
What would you like to be added:
I would like to be able to configure retry budgets in HTTPRouteRetry
Why this is needed:
While #1731 implements HTTPRouteRetry, we still lack the capability to set the retries using a percentage. This was part of #1731 initially but was dropped out of scope later on.
Implementations like Linkerd rely solely on this percentage based budget to implement the retry functionality.
The text was updated successfully, but these errors were encountered: