Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Retry Policy for GRPCRoute #3440

Open
shadialtarsha opened this issue Nov 7, 2024 · 3 comments · May be fixed by #3441
Open

Retry Policy for GRPCRoute #3440

shadialtarsha opened this issue Nov 7, 2024 · 3 comments · May be fixed by #3441
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@shadialtarsha
Copy link

What would you like to be added:
A new field retry needs to be added to GRPCRouteRule which allows specifying the retry policy for a gRPC endpoint https://grpc.io/docs/guides/retry/

Why this is needed:
The current API of the GRPCRoute does not include a mechanism for specifying retry policies:

  1. The addition of a retry policy allows services to automatically recover from transient failures without additional complexity in client implementations.
  2. Ensures developers can implement retry strategies consistently across services.
@shadialtarsha shadialtarsha added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 7, 2024
@shadialtarsha
Copy link
Author

Discussed this in the #sig-netwrok-gateway-api channel with @mikemorris and mentioned that this was originally part of GEP-1731 but it got dropped for scope and time.

@shadialtarsha shadialtarsha linked a pull request Nov 8, 2024 that will close this issue
Open
@mikemorris mikemorris mentioned this issue Jan 30, 2025
Merged
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 5, 2025
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

gep: GEP-3440 - Gateway API Support for gRPC Retries shadialtarsha/gateway-api
3 participants
@k8s-ci-robot @k8s-triage-robot @shadialtarsha