Skip to content

Retry Policy for GRPCRoute #3440

Closed as not planned
Closed as not planned
@shadialtarsha

Description

@shadialtarsha

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions