Backport of Add support for configuring Envoys route idle_timeout into release/1.14.x #15611
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.
Backport
This PR is auto-generated from #14340 to be assessed for backporting due to the inclusion of the label backport/1.14.
WARNING automatic cherry-pick of commits failed. Commits will require human attention.
The below text is copied from the body of the original PR.
Description
This PR adds support for configuring the Envoy route level idle_timeout for service-routers and local_app. For our teams scenario, this will let us extend the timeout for long-running gRPC services so that Envoy doesn't terminate the connection prematurely.
For service-routers a
IdleTimeout
parameter has been added, and for local_app a proxy configlocal_idle_timeout_ms
parameter was created. I followed the RequestTimeout and local_request_timeout_ms definitions closely.Testing & Reproduction steps
Manual Testing Steps
service-router IdleTimeout
Created a service-router and configured the
IdleTimeout
to 60sDumped the Envoy config and verified that the
idle_timeout
configuration parameter was setlocal_idle_timeout_ms
Configure
local_idle_timeout_ms
on a service proxy.configDumped the Envoy config and verified that the
idle_timeout
configuration parameter was set on the public_listener route forlocal_app
Links
Include any links here that might be helpful for people reviewing your PR (Tickets, GH issues, API docs, external benchmarks, tools docs, etc). If there are none, feel free to delete this section.
Please be mindful not to leak any customer or confidential information. HashiCorp employees may want to use our internal URL shortener to obfuscate links.
PR Checklist
Overview of commits