feat(outbound)!: Add retry and timeout route policies #357
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3581e5e to
d238e2d
Compare
This commit adds support for retry and timeout route policies to the outbound policy API to both HTTP and GRPC route types. This change also bumps the release version to v0.14.0 in preparation for the next release. The pre-existing requestTimeout fields are deprecated. The RouteBackend requestTimeout is no longer honored, while the route requestTimeout should correspond to the 'request' timeout policy.
d238e2d to
f61b8d6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds support for retry and timeout route policies to the outbound
policy API to both HTTP and GRPC route types.
This change also bumps the release version to v0.14.0 in preparation for the
next release.
The pre-existing requestTimeout fields are deprecated. The RouteBackend
requestTimeout is no longer honored, while the route requestTimeout should
correspond to the 'request' timeout policy.